dbcve.org
AndroidOperating system · Google

CVE-2023-21347

HIGH · 7.5 CVSS v3.1 Published 2023-10-30
Fix available
A fix is available. Upgrade to 14.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

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 Bluetooth stack due to a missing bounds check. This allows remote attackers to read sensitive memory contents beyond intended buffer boundaries without requiring any user interaction or elevated privileges.

MitigationApply vendor-provided security patches for the Bluetooth stack. Where patches are unavailable, reduce attack surface by disabling Bluetooth when not in use or implementing network-level mitigations to block Bluetooth exploitation vectors.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 is the operating system
    Check device system information via Settings > About Phone, or run 'adb shell getprop ro.build.version.release' and 'adb shell getprop ro.product.model'
    Affected if The device is not running Google Android (e.g., is a different OS or custom ROM) - this CVE only affects Android devices
  2. Check Android version number
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if The installed Android version is 14.0 or higher - versions below 14.0 are within the affected range (< 14.0)
  3. Verify Bluetooth is enabled
    Check Settings > Bluetooth toggle, or run 'adb shell settings get global bluetooth_on' (returns 1 if enabled, 0 if disabled)
    Affected if Bluetooth is currently enabled - the vulnerability exists in the Bluetooth stack, so it must be active to be exploitable
  4. Check security patch level
    Go to Settings > About Phone > Security patch level, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The Security patch level is earlier than April 2023 - Google patched this vulnerability in the April 2023 security update

A device is affected if it runs Google Android version below 14.0, has Bluetooth enabled, and has not received the April 2023 or later Android security 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
Upgrade available Upgrade to 14.0 or later
Fixed in 14.0
Interim mitigation

Apply vendor-provided security patches for the Bluetooth stack. Where patches are unavailable, reduce attack surface by disabling Bluetooth when not in use or implementing network-level mitigations to block Bluetooth exploitation vectors.

Recommended fix High confidence

Android 14.0 (or later security patch level)

  1. Check your Android device's current version by navigating to Settings > About Phone > Android version
  2. Verify if Android 14.0 is available for your specific device model by checking your device manufacturer's support website
  3. Back up all important data, contacts, photos, and files to a secure location
  4. Connect your device to a stable Wi-Fi network and ensure sufficient battery charge (at least 50%)
  5. Navigate to Settings > System > Software Update (or Settings > About Phone > System Update)
  6. Download and install the Android 14.0 security update containing the fix for CVE-2023-21347
  7. After installation, verify the update was successful by checking Settings > About Phone > Android version shows 14.0 or higher
Caveat Major Android version upgrades may cause compatibility issues with older apps or require reconfiguration of device settings; review app compatibility and back up data before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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