dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-11292

HIGH · 7.8 CVSS v3.0 Published 2018-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Snapdragon (Automobile, Mobile, Wear) in version MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, QCA6574AU, QCA6584, 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 820A, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016, lack of input validation in WLANWMI command handlers can lead to integer & heap overflows.

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

This vulnerability exists in Qualcomm Snapdragon chipsets across mobile, automotive, and wearable platforms. The WLAN WMI (Wireless Management Interface) command handlers lack proper input validation, which can be exploited to trigger integer overflows leading to heap overflows. This could allow an attacker to execute arbitrary code or cause denial of service.

MitigationApply vendor firmware/security updates from device manufacturers as they become available. Until patches are applied, limit exposure by restricting network access to affected 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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qca6574au 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model
    Retrieve the chipset identifier using device information commands such as 'getprop' on Android devices, checking /proc/cpuinfo, or using manufacturer diagnostic tools for automotive/wearable devices. Look for identifiers including Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, Qca6574au, or Qca6584.
    Affected if The chipset model matches any of the following: Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, Qca6574au, or Qca6584.
  2. Confirm firmware version
    Query the device firmware version through vendor-specific interfaces such as AT commands on modems, diagnostic ports, or system information menus. Since all firmware versions of the affected chipsets are vulnerable, any non-patched version indicates potential exposure.
    Affected if The device runs any firmware version on one of the affected chipset models without vendor security patches applied.
  3. Verify WLAN/WMI interface status
    Check if the Wireless Management Interface (WMI) is active on the device. On Android, this may be observable through WiFi driver status, wlan service logs, or network interface listings (iwconfig, ip link). On automotive modules, check the WMI daemon or service status.
    Affected if The WLAN interface is enabled and operational, making the WMI command handlers active and exploitable.
  4. Assess network accessibility
    Determine if the affected device is directly accessible from untrusted networks. Check firewall rules, network segmentation, and whether the device exposes management interfaces to LAN or WAN. Review logs for attempted WMI command injection or anomalous wireless traffic.
    Affected if The device with the vulnerable chipset and enabled WLAN is accessible from network segments outside a trusted environment.

The environment is affected if any device contains one of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, Qca6574au, Qca6584) with WLAN functionality enabled and network accessibility, since all firmware versions of these chipsets are vulnerable.

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 vendor firmware/security updates from device manufacturers as they become available. Until patches are applied, limit exposure by restricting network access to affected devices.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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