Security readout for executives and security teams
Plain-English summary
This Android Bluetooth flaw could let a nearby attacker read information from affected Android 12 or Android 12L devices without user interaction or extra privileges. The source bundle does not provide a CVSS score, severity rating, or evidence of active exploitation.
Executive priority
Treat this as a patch governance issue for Android fleets, especially where Bluetooth remains enabled. It is not KEV-listed in the bundle, but no-interaction Bluetooth information disclosure warrants timely verification.
Technical view
CVE-2021-39805 is an out-of-bounds read in Android's Bluetooth L2CAP BLE signaling handler, l2cble_process_sig_cmd in l2c_ble.cc, caused by a missing bounds check. The disclosed impact is remote information disclosure over Bluetooth on Android 12 and Android 12L.
Likely exposure
Exposure is limited to Android 12 and Android 12L devices with vulnerable Bluetooth stack code. Practical exposure depends on device patch level, OEM update status, and whether Bluetooth is enabled or reachable.
Exploitation context
The source states exploitation needs no user interaction and no additional execution privileges. It does not state active exploitation, public exploit availability, attack range, or what information may be disclosed.
Researcher notes
The bundle provides Android ID A-212694559 but no CVSS, CWE, commit, proof of concept, or detailed fixed-build mapping. Avoid claims about exploitability beyond remote Bluetooth information disclosure unless confirmed by vendor material.
Mitigation direction
- Apply Android security updates covering the April 2022 bulletin.
- Confirm OEM firmware includes the relevant Android Bluetooth fix.
- Disable Bluetooth where operationally feasible until patched.
- Prioritize managed Android 12 and 12L devices for patch verification.
Validation and detection
- Inventory Android 12 and 12L devices in the environment.
- Check each device security patch level and OEM bulletin coverage.
- Verify Bluetooth exposure policy for managed devices.
- Track exceptions where devices cannot receive vendor updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-39805 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/2022-04-01CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.