dbcve.org
AndroidOperating system · Google

CVE-2022-20027

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 out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06126826; Issue ID: ALPS06126826.

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 bounds check in the Bluetooth component allows an out-of-bounds write, leading to local privilege escalation without requiring user interaction or additional execution privileges. This is a memory corruption vulnerability in the Bluetooth stack (MediaTek/ALPS components based on patch identifiers).

MitigationApply the vendor patch ALPS06126826 to address the missing bounds check in the Bluetooth component. As this is a local privilege escalation, ensure the patch is prioritized for devices with the affected Bluetooth implementation.

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 use 'getprop ro.build.version.release' via ADB)
    Affected if The version is 8.1, 9.0, 10.0, 11.0, or 12.0
  2. Identify Bluetooth implementation
    Check the device's Bluetooth stack supplier - this vulnerability exists in MediaTek/ALPS Bluetooth components. Consult device documentation or use 'getprop ro.hardware' to identify MediaTek hardware
    Affected if The device uses a MediaTek Bluetooth implementation (ALPS-based)
  3. Verify patch status
    Query the system for applied security patches - on Android this is typically shown in Settings > About Phone > Security patch level, or via 'getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than the one containing ALPS06126826, or the patch is not applied

A device is affected if it runs Android 8.1 through 12.0, uses a MediaTek/ALPS Bluetooth stack, and lacks the ALPS06126826 patch.

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 ALPS06126826 to address the missing bounds check in the Bluetooth component. As this is a local privilege escalation, ensure the patch is prioritized for devices with the affected Bluetooth implementation.

Recommended fix Moderate confidence

Android Security Patch Level containing ALPS06126826 (contact MediaTek chipset OEMs for specific version numbers)

  1. Check your device manufacturer's security update documentation or support pages for availability of the MediaTek Bluetooth patch (ALPS06126826)
  2. Contact your device manufacturer (OEM) to confirm if a security update containing this fix has been released for your specific device model
  3. If a security update is available, apply it through your device's system update mechanism
  4. For devices no longer receiving official security updates, consider migrating to a newer device that receives active security support
  5. Verify the fix was applied by checking your device's Android Security Patch Level in Settings > About Phone > Security Patch Level

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
28.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20027 — 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-20027 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