dbcve.org
AndroidOperating system · Google

CVE-2022-20043

HIGH · 7.8 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In Bluetooth, there is a possible escalation of privilege due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06148177; Issue ID: ALPS06148177.

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 confidence

In Bluetooth, a missing permission check allows a local attacker to escalate privileges without requiring user interaction or additional execution privileges. The vulnerability exists in the Bluetooth component where proper authorization validation is not performed before allowing certain privileged operations.

MitigationApply the vendor patch (ALPS06148177) which adds the missing permission check in the Bluetooth component. Verify that all Bluetooth operations now properly validate caller permissions before executing privileged actions.

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
AndroidOperating system
Affected:= 8.1= 9.0= 10.0= 11.0= 12.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is exactly 8.1, 9.0, 10.0, 11.0, or 12.0
  2. Verify Bluetooth component presence
    Confirm Bluetooth is available on the device by checking Settings > Bluetooth or running 'settings get global bluetooth_on' via ADB shell
    Affected if Bluetooth is present and enabled on the device (the vulnerability exists in the Bluetooth component regardless of current state)
  3. Check security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if The security patch level is earlier than the vendor fix (ALPS06148177) - meaning the missing permission check has not been applied

You are affected if your Android device runs version 8.1, 9.0, 10.0, 11.0, or 12.0 and the Bluetooth component has not received the vendor patch that adds the missing permission check.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (ALPS06148177) which adds the missing permission check in the Bluetooth component. Verify that all Bluetooth operations now properly validate caller permissions before executing privileged actions.

Recommended fix Moderate confidence

May 2022 Android Security Patch Level or later (incorporating MediaTek patch ALPS06148177)

  1. Check your device's current Android security patch level in Settings > About Phone > Android security patch level
  2. Identify if your device uses a MediaTek chipset (check via Settings > About Phone > Processor or chipset information)
  3. Apply the latest Android security update from your device manufacturer - this vulnerability was fixed in the May 2022 Android Security Bulletin (or subsequent patches)
  4. For MediaTek-based devices, ensure your device manufacturer has released an update incorporating MediaTek patch ALPS06148177
  5. If no update is available from your device OEM, consider applying any available system updates or contacting your device vendor for patch availability
  6. Verify the fix by confirming the security patch level includes the May 2022 patch or later after updating
Caveat Security patches typically have minimal breaking changes; however, verify with your device manufacturer before updating if concerned about compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20043 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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