dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14135

HIGH · 7.8 CVSS v3.1 Published 2020-04-16
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
Possible integer overflow to buffer overflow in WLAN while parsing nonstandard NAN IE messages. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8096, APQ8096AU, IPQ8074, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA4010, QCA6174A, QCA6574AU, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9886, QCN7605, QCS405, QCS605, SA6155P, Saipan, SDA845, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SM6150, SM7150, SM8150, 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

Integer overflow vulnerability in WLAN firmware when parsing nonstandard NAN (Neighbor Awareness Networking) Information Element messages. The overflow allows heap or stack buffer overflow, potentially enabling remote code execution or denial of service via malformed WiFi frames.

MitigationApply vendor firmware patches from device manufacturers (Qualcomm Snapdragon). As interim mitigation, disable NAN functionality on affected devices if supported, or restrict WiFi exposure to trusted networks.

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
Apq8096au FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c FirmwareOperating system
Affected:all versions
Mdm9607 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.1/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
    Check the device specifications or system information to determine if the chipset matches any of the following: Apq8009, Apq8017, Apq8053, Apq8096au, Ipq8074, Mdm9206, Mdm9207c, or Mdm9607
    Affected if The chipset is one of the listed affected models
  2. Verify the WLAN firmware version
    Query the WLAN firmware version through the device's diagnostic interface, firmware information utility, or manufacturer documentation
    Affected if The device uses one of the affected chipsets and the firmware is present (all versions are affected according to the advisory)
  3. Confirm NAN functionality is enabled
    Check the WiFi configuration settings or wireless driver parameters to determine if Neighbor Awareness Networking (NAN) is turned on. This may be accessible through wlan driver debug interfaces, config files, or wireless management tools
    Affected if NAN is actively enabled and the device uses an affected chipset
  4. Check for unexpected WiFi behavior
    Monitor wireless interface logs, kernel messages, or firmware crash dumps for signs of heap or stack corruption related to WiFi frame handling, or anomalous device resets after receiving WiFi frames
    Affected if The device exhibits unexplained WiFi crashes or memory corruption events and uses an affected chipset with NAN enabled

A user is affected if their device uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096au, Ipq8074, Mdm9206, Mdm9207c, Mdm9607) and has NAN functionality enabled, since all firmware versions for these chipsets contain the 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 device manufacturers (Qualcomm Snapdragon). As interim mitigation, disable NAN functionality on affected devices if supported, or restrict WiFi exposure to trusted networks.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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