CVE-2017-13211
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 bta_scan_results_cb_impl of btif_ble_scanner.cc, there is possible resource exhaustion if a large number of repeated BLE scan results are received. This could lead to a remote denial of service of a critical system process with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: 8.0. Android ID: A-65174158.
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 confidenceIn the Android Bluetooth stack (btif_ble_scanner.cc), the BLE scan results callback handler (bta_scan_results_cb_impl) lacks proper resource management or throttling when processing incoming BLE advertisement data. An attacker in BLE range can flood the device with a large volume of repeated BLE scan results, causing resource exhaustion (memory/CPU) in the Bluetooth system process, leading to a denial of service crash.
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= 8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify Android version is 8.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version displayed is exactly 8.0 (Oreo)
-
Confirm Bluetooth is enabledCheck Settings > Bluetooth toggle, or run 'settings get global bluetooth_on' via ADB shellAffected if Bluetooth is turned on
-
Check for active BLE scan sessionsRun 'dumpsys bluetooth_manager' or check logcat for 'BLE scan' activity via 'logcat -d | grep -i "bta_scan_results"'Affected if Any app or system service is actively performing BLE scans (continuous scanning observed)
-
Inspect Bluetooth system process resource stateRun 'dumpsys bluetooth' and monitor for high memory usage or CPU consumption in the bluetooth process during active scanningAffected if Bluetooth process shows abnormally high resource usage when BLE scanning is active
A device is affected if it is running Android 8.0 with Bluetooth enabled and any active BLE scanning is occurring, as the vulnerability triggers when the bta_scan_results_cb_impl callback processes incoming BLE advertisements without throttling.
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.
From vendor dataApply the Android security patch for the 2017-12-01 or later CVE bundle (Android 8.0). This is a platform-level vulnerability requiring a system update; no user-facing workarounds are available. Consider BLE scanning app restrictions as a temporary measure.
- Consultation3.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13211 — 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-2017-13211 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