dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-18126

HIGH · 7.5 CVSS v3.0 Published 2018-04-11
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 before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206, MDM9607, MDM9640, MDM9650, QCA6174A, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA9377, QCA9379, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, Snapdragon_High_Med_2016, the original mac spoofing feature does not use the following in probe request frames: (a) randomized sequence numbers and (b) randomized source address for cfg80211 scan, vendor scan and pno scan which may affect user privacy.

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

In affected Qualcomm Snapdragon chipsets, the MAC address randomization feature for Wi-Fi probe request frames fails to use randomized sequence numbers and properly randomized source addresses across cfg80211 scan, vendor scan, and PNO scan operations. This allows passive observers to track devices by correlating predictable MAC addresses and sequence numbers in probe requests.

MitigationApply the Android security patch level 2018-04-05 or later to affected devices, which includes the corrected Wi-Fi driver with proper MAC randomization for all scan types.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions
Qca6574 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Qca6584 FirmwareOperating system
Affected:all versions

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. Identify the Wi-Fi chipset model
    Check the device specifications or system information to determine the Qualcomm chipset model (e.g., Mdm9206, Mdm9607, Qca6174a, Qca6574, Mdm9640, Qca6574au, Mdm9650, Qca6584)
    Affected if The chipset matches any of the affected models listed in the CVE (Mdm9206, Mdm9607, Qca6174a, Qca6574, Mdm9640, Qca6574au, Mdm9650, Qca6584)
  2. Verify the Wi-Fi firmware version
    Use manufacturer tools or system diagnostics to retrieve the Wi-Fi firmware version of the Qualcomm chipset
    Affected if The firmware version is any version (all versions of the affected chipsets are vulnerable)
  3. Confirm Wi-Fi functionality is in use
    Check if Wi-Fi is enabled and actively scanning (probe requests are only sent when Wi-Fi scanning is performed)
    Affected if Wi-Fi is enabled and the device performs scan operations (cfg80211 scan, vendor scan, or PNO scan)
  4. Capture and inspect probe request frames
    Use a Wi-Fi monitor mode capture tool to observe probe request frames from the device and check if the source MAC address and sequence number remain consistent across multiple scans
    Affected if The MAC address in probe requests is not properly randomized between scans, or the sequence numbers follow a predictable pattern

If the device uses any of the affected Qualcomm chipsets (Mdm9206, Mdm9607, Qca6174a, Qca6574, Mdm9640, Qca6574au, Mdm9650, Qca6584) and utilizes Wi-Fi scanning, the MAC address randomization flaw is present since all firmware versions are affected.

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 level 2018-04-05 or later to affected devices, which includes the corrected Wi-Fi driver with proper MAC randomization for all scan types.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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