dbcve.org
AndroidOperating system · Google

CVE-2022-20313

MEDIUM · 6.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 →
70/100
Remediation priority · Elevated
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 System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-192206329

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

This is a memory safety vulnerability in Android's Bluetooth stack where a missing bounds check allows an out-of-bounds write. The flaw could enable local privilege escalation, though exploitation requires System-level execution privileges on the device.

MitigationApply the Android security patch level for September 2022 or later, which includes the fix for this Bluetooth bounds check vulnerability. Organizations should ensure devices receive regular platform updates.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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. Confirm Android version is 13.0
    Go to Settings > About Phone > Android version, or run `getprop ro.build.version.release` via ADB shell
    Affected if The installed Android version is exactly 13.0 (this CVE does not affect other versions)
  2. Verify Bluetooth is enabled
    Go to Settings > Bluetooth, or run `settings get global bluetooth_on` via ADB shell
    Affected if Bluetooth is turned ON (the vulnerability is in the Bluetooth stack, so it only applies when Bluetooth is active)
  3. Check the 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 2022-09-01 (the fix was released in the September 2022 Android security update)
  4. Identify if device has System-level execution
    This CVE requires an app or process with System-level privileges to exploit. Check installed apps for unusually broad permissions via Settings > Apps > Permissions, or review running processes with `ps -A` via ADB shell
    Affected if The device runs third-party apps or services with System-level or elevated Bluetooth permissions

Your device is affected if it runs Android 13.0, has Bluetooth enabled, and has a Security Patch Level earlier than September 2022.

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 for September 2022 or later, which includes the fix for this Bluetooth bounds check vulnerability. Organizations should ensure devices receive regular platform updates.

Recommended fix High confidence

Android 13 with October 2022 security patch level or later (or Android 14 if device upgrade path available)

  1. 1. Check the current Android security patch level on the device by navigating to Settings > About Phone > Android version or Settings > Security > Security patch level
  2. 2. Ensure the device has the October 2022 security patch level or later installed, which contains the fix for CVE-2022-20313
  3. 3. If the October 2022 patch is not available, check for any available system updates in Settings > System > Software Update
  4. 4. Apply all available system updates until the device reaches a security patch level that includes the fix
  5. 5. Verify the fix is applied by confirming the security patch level is October 2022 or later 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
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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