dbcve.org
AndroidOperating system · Google

CVE-2023-21200

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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 on_remove_iso_data_path of btm_iso_impl.h, there is a possible out of bounds read due to improper input validation. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-236688764

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

An out-of-bounds read vulnerability exists in the on_remove_iso_data_path function within the Bluetooth ISO (Ischronous) implementation (btm_iso_impl.h) in Android-13. The issue stems from improper input validation, allowing a local attacker to read sensitive information from memory without requiring elevated privileges or user interaction.

MitigationApply the Google-provided Android security patch for CVE-2023-21200 (Android-13 update) to address the input validation issue in btm_iso_impl.h; there is no user-facing configuration workaround for this Bluetooth stack vulnerability.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Version displays 13.0 exactly (the '=' indicates only this exact version is affected)
  2. Verify Bluetooth is enabled
    Check Settings > Bluetooth toggle, or run 'settings get global bluetooth_on' via ADB shell
    Affected if Bluetooth is turned on (value returns 1) - the vulnerability exists in the active Bluetooth stack
  3. Check for active Bluetooth ISO connections
    Run 'btmon' or check Bluetooth logs via 'logcat | grep -i iso' to detect any isochronous channel activity
    Affected if Any ISO (isochronous) connections are active or have been established since boot
  4. Inspect btm_iso_impl.h usage in Bluetooth stack
    If you have system-level access, examine /system/lib64/libbluetooth.so or corresponding vendor library for the on_remove_iso_data_path function call path
    Affected if The Bluetooth stack processes ISO data path removal operations

A device is affected if it runs Android 13.0 with Bluetooth enabled and processes ISO (isochronous) channel operations, as the out-of-bounds read triggers during ISO data path removal in the Bluetooth stack.

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 Google-provided Android security patch for CVE-2023-21200 (Android-13 update) to address the input validation issue in btm_iso_impl.h; there is no user-facing configuration workaround for this Bluetooth stack vulnerability.

Recommended fix High confidence

Android 13 with latest security update (Android Security Bulletin release containing fix for A-236688764)

  1. 1. Go to Settings on the Android device
  2. 2. Navigate to System > System Update (or Settings > About Phone > Software Update)
  3. 3. Check for and install any available system updates
  4. 4. Ensure the device receives the Android security patch level that includes the fix for A-236688764
  5. 5. After updating, verify the patch level by going to Settings > About Phone > Android version and confirming the security patch date is after the vulnerability disclosure
Caveat Standard Android security update - minimal risk of breaking changes; updates are backward compatible

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-2023-21200 — 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-2023-21200 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