dbcve.org
Ipq8074 FirmwareOperating system · Qualcomm

CVE-2019-10539

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Possible buffer overflow issue due to lack of length check when parsing the extended cap IE header length in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ8074, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA6174A, QCA6574, QCA6574AU, QCA6584, QCA8081, QCA9379, QCS404, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24, SXR1130

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

Buffer overflow vulnerability in multiple Qualcomm Snapdragon chipsets due to missing length validation when parsing the extended capabilities Information Element (IE) header. The lack of bounds checking during IE header parsing allows attackers to overflow buffers, potentially leading to remote code execution or denial of service.

MitigationApply vendor firmware updates from Qualcomm and device manufacturers when available; until patches are deployed, reduce attack surface by filtering untrusted network inputs and monitoring for exploitation attempts.

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
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions
Qca6574 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 chipset model in your device
    Check /proc/cpuinfo, /sys/class/hwmon or device documentation for the Qualcomm chipset identifier (e.g., Ipq8074, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8996au, Qca6174a, Qca6574)
    Affected if The chipset matches any of the affected models listed in CVE-2019-10539
  2. Verify wireless firmware is loaded
    Check if wireless interfaces (wlan0, wlan1, etc.) exist using 'ip link show' or 'ifconfig -a'
    Affected if Wireless interfaces are present and the driver is loaded, indicating the vulnerable IE parsing code is active
  3. Confirm extended capabilities IE parsing is in use
    Monitor network traffic with tcpdump or Wireshark for 802.11 management frames (beacon, probe response, association) containing Extended Capabilities IE (IE ID 127)
    Affected if Extended Capabilities IE is being transmitted or received by the device, meaning the vulnerable parsing function is executing
  4. Check firmware version if accessible
    If you can access the firmware (via bootloader, debug interface, or firmware dump), verify it is a version from the affected product line
    Affected if The device runs Qualcomm firmware based on the affected chipset families without the CVE patch applied

Your environment is affected if the device uses any of the listed Qualcomm chipset models (Ipq8074, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8996au, Qca6174a, Qca6574) and has wireless functionality enabled that parses 802.11 Extended Capabilities IE.

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 updates from Qualcomm and device manufacturers when available; until patches are deployed, reduce attack surface by filtering untrusted network inputs and monitoring for exploitation attempts.

Fix this in Ipq8074 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA10.0 h
58.0 hours of engineering $10,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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