CVE-2021-22952
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability found in UniFi Talk application V1.12.3 and earlier permits a malicious actor who has already gained access to a network to subsequently control Talk device(s) assigned to said network if they are not yet adopted. This vulnerability is fixed in UniFi Talk application V1.12.5 and later.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in UniFi Talk V1.12.3 and earlier allows a network-adjacent attacker who has already gained access to the network to take control of unadopted Talk devices. The flaw appears to be a missing or insufficient authentication/authorization check for Talk devices that have not yet been adopted into the management plane, allowing unauthorized control by anyone with network proximity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.12.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify UniFi Talk installation versionAccess the UniFi Controller interface and navigate to the UniFi Talk section, or check the UniFi Talk software/package version through the controller's device list or system settingsAffected if The installed UniFi Talk version is 1.12.3 or earlier
-
Check for unadopted Talk devicesIn the UniFi Controller, examine the Talk devices list and identify any devices showing as 'unadopted' or 'pending adoption' status - these are devices not yet fully integrated into the management planeAffected if There are one or more Talk devices that remain in an unadopted or pending state in the controller
-
Assess network accessibility of unadopted devicesReview network configuration to determine if the subnet or VLAN containing unadopted Talk devices is accessible to network-adjacent attackers - check if these devices are on an isolated network segment or if they respond to discovery protocols from unauthorized network segmentsAffected if Unadopted Talk devices are reachable from network segments accessible to untrusted or attacker-proximal network users
-
Verify adoption status through controller logsReview UniFi Controller logs or event history for any failed adoption attempts or authentication events related to Talk devices, which may indicate exploitation attempts or configuration issuesAffected if Controller logs show adoption failures or unauthorized access attempts targeting Talk devices
You are affected if UniFi Talk version 1.12.3 or earlier is running AND there are unadopted Talk devices that are accessible to network-adjacent attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate UniFi Talk to V1.12.5 or later to remediate this vulnerability. Prioritize updating deployments with unadopted Talk devices exposed to network-accessible attackers.
UniFi Talk V1.12.5 or later
- Access the UniFi Controller or UniFi OS Console hosting the UniFi Talk application
- Navigate to the UniFi Talk application settings or applications section
- Locate the current UniFi Talk version (confirm it is version 1.12.3 or earlier)
- Upgrade UniFi Talk to version 1.12.5 or later (check for the latest available stable version)
- Verify the upgrade was successful by confirming the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22952 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data