dbcve.org
AndroidOperating system · Google

CVE-2017-13267

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_pars_vendor_cmd of avrc_pars_tg.cc, there is a possible stack corruption due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-69479009.

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

Stack-based buffer overflow in the Bluetooth AVRCP vendor command parser (avrc_pars_vendor_cmd in avrc_pars_tg.cc) due to missing bounds checking. The vulnerability allows remote code execution with kernel-level privileges via specially crafted Bluetooth AVRCP packets, requiring no user interaction or additional privileges.

MitigationApply the Android security patch from the relevant monthly security bulletin (refer to Android Security Bulletin for the fix). The vulnerability is in the Bluetooth stack and requires system-level patching; disabling Bluetooth reduces attack surface but is not a practical long-term mitigation.

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:= 6.0= 6.0.1= 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 Settings > System > About Phone > Android version) and note the exact version number
    Affected if The version is 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1
  2. Check security patch level
    Go to Settings > About Phone > Android security patch level (or Settings > System > About Phone > Security patch level)
    Affected if The patch level is earlier than the fix release for this CVE (refer to the Android Security Bulletin for the specific month the fix was released)
  3. Verify Bluetooth status
    Check if Bluetooth is currently enabled on the device via Settings > Bluetooth or the quick settings panel
    Affected if Bluetooth is enabled - the vulnerability exists in the Bluetooth stack and can be exploited when Bluetooth is active

The device is affected if it runs Android 6.0 through 8.1 and has not received the security patch that fixes this Bluetooth AVRCP buffer overflow.

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 from the relevant monthly security bulletin (refer to Android Security Bulletin for the fix). The vulnerability is in the Bluetooth stack and requires system-level patching; disabling Bluetooth reduces attack surface but is not a practical long-term mitigation.

Recommended fix High confidence

Android 8.0 or later, or ensure the device has the January 2018 security patch level applied

  1. Upgrade the Android device to a version that includes the security patch for CVE-2017-13267. Based on the Android security bulletin, this vulnerability was addressed in the January 2018 security patch level.
  2. If upgrading to a newer Android version is not possible, ensure the device receives the monthly security update that includes the fix for A-69479009.
  3. Verify the device's security patch level is at least January 2018 or later by checking Settings > About Phone > Security Patch Level.
Caveat Upgrading to a newer Android version may cause compatibility issues with older applications or device features; some devices may not receive further updates due to end-of-life status

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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