dbcve.org
AndroidOperating system · Google

CVE-2017-11064

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-36815952. References: QC-CR#2054770, QC-CR#2058447, QC-CR#2066628, QC-CR#2087785

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 · moderate confidence

A buffer overread vulnerability exists in the cfg80211 vendor command handling for passpoint list configuration in Android's WiFi subsystem. The flaw occurs in __wlan_hdd_cfg80211_set_passpoint_list and hdd_extscan_passpoint_fill_network_list functions when processing ACA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_SET_PASSPOINT_LIST and QCA_NL80211_VENDOR_SUBCMD_EXTSCAN_PNO_SET_LIST vendor commands, allowing memory content disclosure beyond buffer boundaries.

MitigationApply the Qualcomm CAF patch or Android monthly security update containing the fix; device vendors should push available kernel-level security patches to affected MSM-based devices.

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. Confirm Android version is 8.0
    Check system settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version equals 8.0 exactly (not 8.0.1 or other) - the vulnerability is specific to Android 8.0
  2. Identify if device uses Qualcomm WiFi driver
    Check the WiFi driver in use via 'getprop ro.wifi.driver' or inspect kernel modules with 'ls /system/lib/modules/' and look for Qualcomm cfg80211 modules
    Affected if Device uses a Qualcomm-based WiFi driver (common on MSM chipset devices) - the vulnerable code resides in Qualcomm's implementation of cfg80211 vendor commands
  3. Verify WiFi is enabled and ExtScan/Passpoint features are in use
    Check WiFi is turned on, then inspect system logs via 'logcat -d | grep -i extscan' or 'logcat -d | grep -i passpoint' to see if ExtScan or Passpoint list operations have been invoked
    Affected if WiFi is enabled AND the device has performed Passpoint list configuration operations (ExtScan PNO set list) - the vulnerability triggers when processing these vendor commands
  4. Inspect kernel logs for memory overread indicators
    Run 'dmesg' or check /sys/kernel/debug/kmsg for any suspicious memory access errors, buffer overread warnings, or unexpected memory content in WiFi-related messages
    Affected if Kernel logs show buffer overread errors, memory access violations, or unexpected memory content associated with cfg80211 vendor command processing

A user is affected if running Android 8.0 with a Qualcomm WiFi driver that has processed Passpoint/ExtScan list configuration commands, as the buffer overread occurs specifically in those 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 Qualcomm CAF patch or Android monthly security update containing the fix; device vendors should push available kernel-level security patches to affected MSM-based devices.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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