dbcve.org
AndroidOperating system · Google

CVE-2017-13282

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-04
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 avrc_ctrl_pars_vendor_rsp of avrc_pars_ct.cc, there is a possible stack buffer overflow 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: Android. Versions: 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-71603315.

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 stack buffer overflow vulnerability exists in the Bluetooth AVRCP (Audio/Video Remote Control Profile) vendor response parser function (avrc_ctrl_pars_vendor_rsp in avrc_pars_ct.cc). The function fails to perform bounds checking on data before copying it to a stack-allocated buffer, allowing an attacker within Bluetooth range to inject and execute arbitrary code without user interaction or elevated privileges.

MitigationApply the Android security patch level for the affected versions (7.0, 7.1.1, 7.1.2, 8.0, 8.1) that addresses CVE-2017-13282. As a defense-in-depth measure, disable Bluetooth when not in use to reduce the 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:= 7.0= 7.1.1= 7.1.2= 8.0= 8.1

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.0/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. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is 7.0, 7.1.1, 7.1.2, 8.0, or 8.1
  2. Verify Bluetooth is enabled
    Check Settings > Bluetooth toggle, or run 'settings get global bluetooth_on' via ADB shell (returns 1 if enabled)
    Affected if Bluetooth is currently turned on - this is required for the attack surface to exist
  3. Check Android security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if The patch level is earlier than January 2018 for Android 7.x or earlier than the respective patch for Android 8.0/8.1, indicating the CVE has not been addressed

The device is affected if it runs Android 7.0, 7.1.1, 7.1.2, 8.0, or 8.1 with Bluetooth enabled and has a security patch level predating the CVE 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch level for the affected versions (7.0, 7.1.1, 7.1.2, 8.0, 8.1) that addresses CVE-2017-13282. As a defense-in-depth measure, disable Bluetooth when not in use to reduce the attack surface.

Recommended fix High confidence

Android 8.1 or later with June 2018 Security Patch Level; or migrate to a currently supported Android version with regular security updates

  1. Check current Android security patch level on the device (Settings > About Phone > Security patch level)
  2. Ensure the security patch level is June 2018 or later, which contains the fix for CVE-2017-13282
  3. If the device is on Android 7.0, 7.1.1, 7.1.2, 8.0, or 8.1, check if the OEM has released a security update containing the June 2018 patch level
  4. If no update is available from the OEM, consider upgrading to a newer Android version (8.1, 9, 10, or later) that receives security updates
  5. For enterprise environments, ensure Bluetooth is disabled if the device cannot be updated
  6. Verify the fix by confirming the device has the June 2018 Android Security Patch Level (or later) applied
Caveat Upgrading to a newer Android version may remove support for older apps or cause compatibility issues with legacy systems; some devices may not receive OEM updates

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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