dbcve.org
AndroidOperating system · Google

CVE-2023-21307

MEDIUM · 5.0 CVSS v3.1 Published 2023-10-30
Fix available
A fix is available. Upgrade to 14.0 or later.
See remediation →
50/100
Remediation priority · Moderate

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 way for a paired Bluetooth device to access a long term identifier for an Android device due to a permissions bypass. This could lead to local information disclosure with no additional execution privileges needed. User interaction is 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

In Android's Bluetooth implementation, a permissions bypass allows a previously paired Bluetooth device to access a long-term identifier for the Android device. This exposes sensitive identifier information locally without requiring additional execution privileges, though user interaction is required to establish or interact with the paired device.

MitigationApply Android security patches promptly, particularly the Google Pixel or OEM-specific security updates containing the fix for this Bluetooth permissions bypass. Users should review paired device lists and remove unrecognized Bluetooth pairings.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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. Check Android version
    Go to Settings > About Phone > Android version (or use `getprop ro.build.version.release` via ADB)
    Affected if Android version is below 14.0
  2. Verify Bluetooth is enabled
    Check Settings > Bluetooth to confirm Bluetooth is turned on, or query via ADB: `adb shell settings get global bluetooth_on`
    Affected if Bluetooth is currently enabled on the device
  3. Review paired Bluetooth devices
    Navigate to Settings > Bluetooth > Paired devices (or use `adb shell bluetooth_manager list_devices` on some devices)
    Affected if One or more previously paired Bluetooth devices exist on the device
  4. Check security patch level
    Go to Settings > About Phone > Security patch level (or use `adb shell getprop ro.build.version.security_patch`)
    Affected if Security patch level is earlier than the patch containing the CVE-2023-21307 fix (the fix is included in Android 14 and subsequent security updates)

A device is affected if it runs Android version below 14.0, has Bluetooth enabled, and has at least one previously paired Bluetooth device, with a security patch level predating the fix.

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 Android security patches promptly, particularly the Google Pixel or OEM-specific security updates containing the fix for this Bluetooth permissions bypass. Users should review paired device lists and remove unrecognized Bluetooth pairings.

Recommended fix High confidence

Android 14.0 or later

  1. Check the current Android version by going to Settings > About Phone > Android version
  2. Back up important data, contacts, photos, and app data to a secure location
  3. Connect device to a stable Wi-Fi network and ensure battery is charged above 50%
  4. Go to Settings > System > Software Update (or Settings > About Phone > System Update)
  5. Check for updates and download Android 14.0 or later if available
  6. Follow on-screen prompts to install the system update
  7. After installation, verify the fix by checking Settings > About Phone shows Android 14.0 or higher
Caveat Android 14 may have app compatibility changes; some legacy apps may require updates

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

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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