CVE-2023-21360
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 · uneditedIn Bluetooth, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege with System 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 confidenceAn out-of-bounds write vulnerability exists in the Bluetooth component due to improper input validation. This allows a local attacker with System-level privileges to execute arbitrary code and escalate privileges further. The flaw does not require user interaction for exploitation.
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= 14.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Android version is 14.0Run 'adb shell getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version returned is exactly 14.0 (not 13.x, 12.x, or 14.1+)
-
Verify Bluetooth component is presentRun 'adb shell pm list features | grep bluetooth' or check that /system/lib64/libbluetooth.so exists on the deviceAffected if Bluetooth feature is listed or the Bluetooth library file exists on the device
-
Confirm System-level access exists on the deviceRun 'adb shell whoami' or check process UID - the vulnerability requires an attacker with System-level privileges to escalate furtherAffected if The device has an account or process running with System-level (UID 1000) but not root (UID 0) privileges
The device is affected if it is running Android version 14.0 exactly and has the Bluetooth component present, as the vulnerability allows a System-level attacker to escalate to root privileges.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-supplied security patch for this vulnerability in the Bluetooth stack. Since this is a system-level privilege escalation, ensure the device is running a supported Android version with the latest security updates.
Android 14.0 with the security patch level that includes the CVE-2023-21360 fix (typically the January 2024 or subsequent Android Security Bulletin)
- Check the Android Security Bulletin for CVE-2023-21360 at source.android.com to identify the specific Android Security Patch Level that contains the fix
- Apply the monthly security update that addresses CVE-2023-21360 to your Android 14.0 device
- Verify the update was successfully installed by checking Settings > About Phone > Security Patch Level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-21360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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