dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14031

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-05
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
Buffer overflow can occur while parsing RSN IE containing list of PMK ID`s which are more than the buffer size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8064, APQ8096, APQ8096AU, APQ8098, IPQ6018, IPQ8074, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8996, MSM8996AU, MSM8998, Nicobar, QCA4531, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9886, QCN7605, QCS405, QCS605, SA6155P, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

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 the RSN IE (Robust Security Network Information Element) parsing functionality of multiple Qualcomm Snapdragon chipset families. The overflow occurs when parsing RSN IE containing a list of PMK IDs (Pairwise Master Key Identifiers) that exceeds the allocated buffer size, potentially allowing remote code execution or denial of service.

MitigationApply vendor firmware patches from Qualcomm and device manufacturers to address the RSN IE parsing buffer overflow. Until patches are available, restrict network exposure of affected devices and monitor 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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8064 FirmwareOperating system
Affected:all versions
Apq8096 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq6018 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 chipset model
    Determine the Qualcomm Snapdragon chipset model used in the device (e.g., via /proc/cpuinfo, lspci, or device documentation)
    Affected if The chipset is one of: Apq8009, Apq8017, Apq8053, Apq8064, Apq8096, Apq8096au, Apq8098, or Ipq6018
  2. Verify WiFi/WLAN is enabled
    Check if the device has WiFi functionality active (via ifconfig, iwconfig, or similar network tools)
    Affected if WiFi interface exists and is up/running
  3. Confirm RSN IE processing capability
    Verify the device supports 802.11 WiFi security features (WPA/WPA2/WPA3) - RSN IE is part of Robust Security Network parsing for these protocols
    Affected if The device operates as a WiFi access point, station, or ad-hoc mode and processes 802.11 authentication/association frames
  4. Check firmware version
    If accessible, query the WiFi firmware version via firmware utilities, debug interfaces, or vendor-specific tools provided by the device manufacturer
    Affected if All firmware versions of the affected chipsets are vulnerable, so any version confirms exposure

If the device uses any of the listed Qualcomm chipset models and has WiFi functionality enabled, it is affected by this vulnerability.

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 patches from Qualcomm and device manufacturers to address the RSN IE parsing buffer overflow. Until patches are available, restrict network exposure of affected devices and monitor for exploitation attempts.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing20.0 h
  • Review / QA12.0 h
72.0 hours of engineering $12,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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