dbcve.org
AndroidOperating system · Google

CVE-2022-20362

HIGH · 8.8 CVSS v3.1 Published 2022-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 an integer overflow. This could lead to remote code execution over Bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-230756082

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

Out of bounds write vulnerability in Android's Bluetooth stack caused by an integer overflow, allowing remote code execution over Bluetooth without user interaction or additional privileges.

MitigationApply the Android security patch level that addresses this vulnerability (Android-13 security updates). For development/custom Android implementations, audit Bluetooth stack code for integer overflow conditions in size/length calculations before memory allocation operations.

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:= 13.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 Version is exactly 13.0 (the affected version listed)
  2. Verify Bluetooth is enabled
    Check if Bluetooth is turned on in Settings > Bluetooth, or run 'settings get global bluetooth_on' via ADB shell
    Affected if Bluetooth is enabled - the vulnerability exists in the Bluetooth stack code itself
  3. Check installed 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 patch level is earlier than the Android-13 security update that addresses this CVE (should be after the fix date)
  4. Confirm Bluetooth stack is active
    Verify the Bluetooth service is running via 'dumpsys bluetooth_manager' or checking BluetoothAdapter status in Settings
    Affected if The Bluetooth service is active and reachable over Bluetooth - the attack vector requires the Bluetooth stack to be handling incoming data

You are affected if running Android 13.0 with Bluetooth enabled and without the relevant Android-13 security patch applied; the integer overflow in the Bluetooth stack becomes exploitable when processing incoming Bluetooth data.

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 Android security patch level that addresses this vulnerability (Android-13 security updates). For development/custom Android implementations, audit Bluetooth stack code for integer overflow conditions in size/length calculations before memory allocation operations.

Recommended fix High confidence

Android 13.0 with September 2022 security patch level (or later monthly patch)

  1. Check your device for system updates and ensure you have the latest Android security patch installed
  2. Go to Settings > System > System Update (or Settings > About Phone > System Update)
  3. Ensure the security patch level is September 2022 or later
  4. If no update is available, contact your device manufacturer or carrier for the security patch
  5. For devices no longer receiving official updates, consider migrating to a device with active security support
Caveat Ensure device is within the supported update window; some older devices may no longer receive monthly security patches

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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