dbcve.org
Apq8096 FirmwareOperating system · Qualcomm

CVE-2019-14097

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
Possible buffer overflow in WLAN Parser due to lack of length check when copying data 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 APQ8096, APQ8096AU, APQ8098, IPQ6018, IPQ8074, MDM9607, MDM9640, MDM9650, MSM8996AU, MSM8998, Nicobar, QCA6174A, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCN7605, QCS405, QCS605, Rennell, SA6155P, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, 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 WLAN parser component of multiple Qualcomm Snapdragon chipsets. The flaw stems from missing length validation checks when copying data, allowing an attacker to overflow buffers and potentially execute arbitrary code or cause denial of service.

MitigationApply firmware updates from device vendors once available. Contact original equipment manufacturers for patch availability and scheduling. For network infrastructure, restrict WLAN processing to trusted inputs until updates are deployed.

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
Apq8096 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq6018 FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 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
    Check the device documentation, system information, or boot logs to determine the exact Qualcomm chipset model (e.g., Apq8096, Ipq6018, Mdm9607). This may be displayed in /proc/cpuinfo, device info pages, or hardware specifications.
    Affected if The chipset matches any of the following: Apq8096, Apq8096au, Apq8098, Ipq6018, Ipq8074, Mdm9607, Mdm9640, or Mdm9650.
  2. Locate the firmware version
    Retrieve the installed firmware version from the device settings, boot logs, or firmware management interface. Consult the device vendor documentation for the specific command or location (often accessible via diagnostic ports, admin panels, or AT commands on modems).
    Affected if The firmware version cannot be determined or is older than any vendor-supplied patch for this CVE.
  3. Confirm WLAN feature is enabled
    Check the device network settings or wireless configuration to verify whether the WLAN (Wi-Fi) functionality is active. This may be via the web interface, CLI, or system status pages.
    Affected if WLAN is enabled and the device uses the affected Qualcomm WLAN parser component.
  4. Check for vendor patch status
    Contact the original equipment manufacturer (OEM) or device vendor to confirm whether a security patch addressing CVE-2019-14097 has been applied to the installed firmware version.
    Affected if The vendor has not released or applied a patch for this specific CVE.

The environment is affected if the device uses one of the listed Qualcomm chipsets (Apq8096, Apq8096au, Apq8098, Ipq6018, Ipq8074, Mdm9607, Mdm9640, Mdm9650), has WLAN enabled, and is running firmware without the vendor patch for this buffer overflow 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 firmware updates from device vendors once available. Contact original equipment manufacturers for patch availability and scheduling. For network infrastructure, restrict WLAN processing to trusted inputs until updates are deployed.

Fix this in Apq8096 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing16.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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