dbcve.org
AndroidOperating system · Google

CVE-2017-13257

MEDIUM · 6.5 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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 bta_pan_data_buf_ind_cback of bta_pan_act.cc there is a use after free that can result in an out of bounds read of memory allocated via malloc. This could lead to information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android. Versions: 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-67110692.

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 use-after-free vulnerability exists in the bta_pan_data_buf_ind_cback callback function within the Android Bluetooth PAN (Personal Area Network) component. The function accesses memory that has already been freed, leading to an out-of-bounds read of previously allocated heap memory. This can result in information disclosure. Exploitation requires user interaction and is achievable without elevated privileges.

MitigationApply the Android security patch released for this vulnerability. The fix requires correcting the memory management in the bta_pan_data_buf_ind_cback function to ensure buffer pointers are not accessed after being freed. Users should apply available security updates promptly.

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:= 5.1.1= 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 your Android version
    Go to Settings > About Phone (or About Device) and look at the Android version field. Alternatively, run `getprop ro.build.version.release` in a terminal or ADB shell.
    Affected if The version equals 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1 exactly.
  2. Verify Bluetooth is enabled
    Check if Bluetooth is turned on in your device settings or run `settings get global bluetooth_on` via ADB shell.
    Affected if Bluetooth is enabled, as the vulnerable code path is triggered when PAN functionality is active.
  3. Check PAN (Personal Area Network) usage
    Inspect if PAN profile is in use or if tethering (Bluetooth tethering or Wi-Fi direct) is active. On Android, you can check via `dumpsys bluetooth_manager` or look at active Bluetooth connections in Settings > Bluetooth > Paired devices.
    Affected if Bluetooth PAN or tethering functionality is actively being used, as the bta_pan_data_buf_ind_cback callback is exercised during PAN data buffer operations.
  4. Confirm the vulnerable component is loaded
    The vulnerable bta_pan_data_buf_ind_cback function resides in the Bluetooth PAN service. This component loads when PAN profile is available. There is no direct user-accessible check for this specific function; the primary indicator is meeting both version and usage conditions.
    Affected if You are on an affected Android version AND using Bluetooth PAN features.

You are affected if your device runs Android 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1 AND you have Bluetooth enabled with PAN/tethering functionality in use.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch released for this vulnerability. The fix requires correcting the memory management in the bta_pan_data_buf_ind_cback function to ensure buffer pointers are not accessed after being freed. Users should apply available security updates promptly.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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