dbcve.org
AndroidOperating system · Google

CVE-2020-0354

CRITICAL · 9.8 CVSS v3.1 Published 2020-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-143604331

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 · high confidence

A missing bounds check in the Android Bluetooth stack allows an out of bounds write, enabling remote code execution without user interaction or elevated privileges. The vulnerability exists in Android-11's Bluetooth component and can be exploited remotely.

MitigationApply the Android-11 security patch that addresses CVE-2020-0354. Until patched, minimize Bluetooth usage and disable Bluetooth visibility to untrusted devices to reduce attack surface.

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:= 11.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Android version is 11.0
    Go to Settings > About Phone > Android version. Confirm the version reads exactly 11.0. On some devices, tap the Android version repeatedly to access build number, then compare.
    Affected if The device runs Android version 11.0 exactly. Later Android versions (11.0.1, 11.0.2, 12+) are not affected by this specific CVE.
  2. Confirm Bluetooth is enabled
    Go to Settings > Bluetooth or pull down the quick settings panel. Check if the Bluetooth toggle is set to ON.
    Affected if Bluetooth must be turned ON for this vulnerability to be exploitable. If Bluetooth is OFF, the attack surface does not exist.
  3. Check Bluetooth visibility settings
    In Settings > Bluetooth > Device name or Bluetooth settings, look for visibility options such as 'Visible to all nearby devices' or 'Timeout' settings. Check if Bluetooth is currently discoverable or was set to be visible within the last few minutes.
    Affected if Bluetooth is discoverable or set to remain visible to nearby devices, allowing remote attackers to reach the device. Even if not actively visible, paired devices with active connections could be vectors.
  4. Check for active Bluetooth connections
    In Settings > Bluetooth, review the list of paired devices. Look for currently connected or paired devices, especially unknown or untrusted devices.
    Affected if Any active Bluetooth connection represents an active attack surface. A remote attacker could exploit the vulnerability during active Bluetooth communication.

If the device runs Android 11.0 and has Bluetooth enabled (whether visible or connected to any device), the device is affected by CVE-2020-0354.

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-11 security patch that addresses CVE-2020-0354. Until patched, minimize Bluetooth usage and disable Bluetooth visibility to untrusted devices to reduce attack surface.

Recommended fix Moderate confidence

Android 11 with Android Security Patch Level 2020-09-01 or later (or upgrade to Android 12/13)

  1. Check for and install the latest Android system update on your device
  2. Go to Settings > System > System Update > Check for updates
  3. If an update is available, download and install it
  4. After updating, verify the Android Security Patch Level is later than the affected version
  5. Alternatively, consider upgrading to a newer Android version (Android 12 or later) which includes the fix and ongoing security support
Caveat Newer Android versions may have compatibility issues with older apps or changes to system behavior; ensure critical apps are compatible before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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