LiveActive security incident?Get immediate response
CVE Record

CVE-2022-20361: In btif_dm_auth_cmpl_evt of btif_dm.cc, there is a possible vulnerability in Cross-Transport Key Derivation...

In btif_dm_auth_cmpl_evt of btif_dm.cc, there is a possible vulnerability in Cross-Transport Key Derivation due to Weakness in Bluetooth Standard. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-231161832

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-20361 affects Android Bluetooth handling. A nearby attacker could potentially abuse Cross-Transport Key Derivation behavior to gain elevated access without user interaction. The issue is not described as internet-exploitable, but it matters for managed Android fleets, especially devices using Bluetooth in public or shared spaces.

Executive priority

Treat this as a moderate-priority mobile fleet issue. It is proximity-limited, but requires no user interaction and may expose sensitive data. Update affected Android devices through normal security patch channels and prioritize high-risk environments.

Technical view

The flaw is in Android btif_dm_auth_cmpl_evt in btif_dm.cc and relates to Cross-Transport Key Derivation weakness in the Bluetooth standard. The CVSS 3.1 vector is AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, meaning adjacent access, low complexity, no privileges, no user interaction, and high confidentiality impact.

Likely exposure

Exposure is limited to affected Android 10, 11, 12, and 12L devices, especially where Bluetooth is enabled. The adjacent attack vector suggests an attacker must be within Bluetooth range rather than remote over the internet.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. Public evidence here supports potential nearby Bluetooth-based exploitation without user interaction, but does not provide confirmed exploitation in the wild.

Researcher notes

Evidence is concise and Android-specific. The weakness is tied to Bluetooth Cross-Transport Key Derivation and Android’s btif_dm_auth_cmpl_evt handling. Sources do not name exploit tooling, detailed prerequisites beyond adjacent access, or non-Android affected products.

Mitigation direction

  • Apply Android security updates covering the August 2022 bulletin or later.
  • Confirm OEM firmware includes a fix for Android ID A-231161832.
  • Prioritize updates for devices with Bluetooth enabled in public environments.
  • Where updates are unavailable, review vendor guidance for compensating controls.

Validation and detection

  • Inventory devices running Android 10, 11, 12, or 12L.
  • Check each device security patch level against the August 2022 Android bulletin.
  • Confirm vendor advisories reference CVE-2022-20361 or A-231161832.
  • Review fleet policy for Bluetooth usage on unsupported or unpatched devices.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-20361 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-20361Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid-10 Android-11 Android-12 Android-12LListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.