dbcve.org
AndroidOperating system · Google

CVE-2017-11060

HIGH · 7.5 CVSS v3.0 Published 2017-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, a buffer overread is observed during processing of ACA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_SET_PASSPOINT_LIST and QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_SET_LIST cfg80211 vendor commands in __wlan_hdd_cfg80211_set_passpoint_list and hdd_extscan_passpoint_fill_network_list function respectively. Android ID: A-36817548. References: QC-CR#2058447, QC-CR#2054770.

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 buffer overread vulnerability exists in the Android kernel's WiFi subsystem (cfg80211) when processing NL80211 vendor commands for Passpoint/PNO (Preferred Network Offload) list configuration. The vulnerability occurs in __wlan_hdd_cfg80211_set_passpoint_list and hdd_extscan_passpoint_fill_network_list functions, where insufficient bounds checking allows reading beyond allocated buffer boundaries.

MitigationApply the vendor-provided kernel patch (QC-CR#2058447, QC-CR#2054770) to add proper length validation in the affected cfg80211 vendor command handlers. Alternatively, update the device to an Android security patch level that includes this fix.

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:= 8.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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Verify Android version is exactly 8.0
    Check the device settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version shows 8.0 exactly - this is the only affected version per the CVE scope
  2. Confirm WiFi subsystem is active
    Check if WiFi is enabled on the device or run 'ip link show wlan0' via ADB to verify the WiFi interface exists
    Affected if WiFi is enabled and the wlan0 interface is present - the vulnerability resides in the cfg80211 WiFi driver
  3. Identify if Passpoint or PNO features are in use
    Check WiFi configuration for saved Passpoint networks (Settings > WiFi > Menu > Advanced > Passpoint) or PNO (Preferred Network Offload) settings, or inspect /data/misc/wifi/wpa_supplicant.conf
    Affected if Passpoint networks are configured or PNO is enabled - these trigger the vulnerable __wlan_hdd_cfg80211_set_passpoint_list and hdm_extscan_passpoint_fill_network_list code paths
  4. Check for NL80211 vendor command handling in kernel
    Examine the kernel cfg80211 module or driver files for functions named '__wlan_hdd_cfg80211_set_passpoint_list' and 'hdd_extscan_passpoint_fill_network_list' - these contain the vulnerable bounds checking
    Affected if The device runs a kernel containing these specific functions without the QC-CR#2058447 or QC-CR#2054770 patches applied

A defender is affected if the device runs Android 8.0 with WiFi enabled and has Passpoint/PNO network configurations, using a kernel that still contains the unpatched cfg80211 vendor command handlers.

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 vendor-provided kernel patch (QC-CR#2058447, QC-CR#2054770) to add proper length validation in the affected cfg80211 vendor command handlers. Alternatively, update the device to an Android security patch level that includes this fix.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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