dbcve.org
AndroidOperating system · Google

CVE-2022-20126

HIGH · 7.3 CVSS v3.1 Published 2022-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 setScanMode of AdapterService.java, there is a possible way to enable Bluetooth discovery mode without user interaction due to a missing permission check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-203431023

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 · high confidence

A missing permission check in the setScanMode function of Android's AdapterService.java allows a local application to enable Bluetooth discovery mode without user interaction. This bypasses the normal authorization mechanism, enabling a local attacker to escalate privileges by making the device discoverable to other Bluetooth devices.

MitigationApply the June 2022 Android Security Bulletin patch (or later) which adds the missing permission check to the setScanMode function in AdapterService.java.

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:= 10.0= 11.0= 12.0= 12.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 the Android OS version
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if The version shows 10.0, 11.0, 12.0, or 12.1 (or any version between 10.0 and 12.1 inclusive that matches the affected range)
  2. Check the installed security patch level
    Go to Settings > About Phone > Security patch level, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than June 2022, or shows a date before 2022-06-05
  3. Verify Bluetooth is enabled and discoverable
    Check if Bluetooth is turned on and the device is in discoverable mode by going to Settings > Bluetooth, or by inspecting Bluetooth adapter state via 'adb shell dumpsys bluetooth_adapter'
    Affected if Bluetooth is enabled and the device is discoverable without explicit user authorization having been granted recently

You are affected if your device runs Android 10.0, 11.0, 12.0, or 12.1 and has not received the June 2022 Android Security Bulletin patch (security patch level earlier than 2022-06).

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 June 2022 Android Security Bulletin patch (or later) which adds the missing permission check to the setScanMode function in AdapterService.java.

Recommended fix High confidence

July 2022 Android Security Patch Level (2022-07-01) or later for Android 10, 11, 12, and 12L

  1. Check your Android device's current security patch level in Settings > About Phone > Security Patch Level
  2. Ensure your device has the July 2022 security patch (2022-07-01) or later installed
  3. Go to Settings > System > System Update to check for and install available updates
  4. If no update is available, contact your device manufacturer or carrier for patch availability information
  5. For enterprise-managed devices, apply the July 2022 Android Security Patch Level through your mobile device management (MDM) console
Caveat Devices no longer receiving monthly security updates may require firmware update from manufacturer or consideration of device replacement

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-20126 — 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-20126 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