CVE-2022-20025
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 · uneditedIn 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: ALPS06126832; Issue ID: ALPS06126832.
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 confidenceA missing bounds check in the Bluetooth component allows an out-of-bounds write, enabling local privilege escalation without requiring additional execution privileges or user interaction. The vulnerability stems from insufficient input validation in memory operations within the Bluetooth stack.
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= 8.1= 9.0= 10.0= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone (or About Device) > Android version. Alternatively, 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
-
Verify Bluetooth is enabledCheck if Bluetooth is turned on in Settings > Bluetooth, or run `settings get global bluetooth_on` via ADB shell (returns 1 if enabled, 0 if disabled).Affected if Bluetooth is enabled on the device (vulnerability resides in the Bluetooth component)
-
Confirm Bluetooth component is presentCheck for the Bluetooth stack by verifying the presence of Bluetooth APK or service. Run `pm list packages | grep bluetooth` via ADB shell.Affected if The Bluetooth package is installed on the device
A device is affected if it runs Android version 8.1, 9.0, 10.0, 11.0, or 12.0 and has Bluetooth enabled, as the out-of-bounds write vulnerability exists in the Bluetooth component of these specific versions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch (ALPS06126832) to implement proper bounds checking. As a temporary measure, consider disabling the Bluetooth feature if the patch cannot be immediately deployed.
- Contact your device manufacturer (OEM) to request the security update containing MediaTek patch ALPS06126832
- Verify your device has the latest Android Security Patch Level that includes the CVE-2022-20025 fix
- For enterprise environments, check Mobile Device Management (MDM) for available security updates
- If no update is available from your OEM, consider whether the device can be replaced or isolated given the Bluetooth attack vector
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20025 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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