dbcve.org
Ipq8074 FirmwareOperating system · Qualcomm

CVE-2019-14082

CRITICAL · 9.1 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
Potential buffer over-read due to lack of bound check of memory offset passed in WLAN firmware in Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in IPQ8074, MDM9206, MDM9207C, MDM9607, QCN7605, SM8150

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 · moderate confidence

Buffer over-read vulnerability in Qualcomm WLAN firmware due to missing bounds validation on a memory offset parameter. The lack of bound checking allows reading beyond allocated buffer boundaries, potentially exposing sensitive memory contents or enabling further exploitation.

MitigationObtain and deploy patched WLAN firmware updates from Qualcomm for affected chip generations (IPQ8074, MDM9206, MDM9207C, MDM9607, QCN7605, SM8150). Coordinate with downstream device manufacturers to ensure firmware propagation.

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
Mdm9207c FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Qcn7605 FirmwareOperating system
Affected:all versions
Sm8150 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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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's system information or kernel messages (dmesg) for the Qualcomm chipset identifier. Common locations: /proc/cpuinfo, /sys/class/hwmon/, or running 'dmesg | grep -i qualcomm' or 'lspci' for network controllers.
    Affected if The chipset matches one of the affected models: IPQ8074, MDM9206, MDM9207C, MDM9607, QCN7605, or SM8150.
  2. Locate the WLAN firmware version
    Query the installed WLAN firmware version through the wireless driver interface. Common methods: 'iw version', 'wpa_supplicant -v', check /lib/firmware/ or /etc/firmware/ for wlan firmware files, or use 'cat /sys/class/net/wlan*/device/firmware_version' if available.
    Affected if The device has WLAN firmware loaded and the version cannot be confirmed as patched (note: all versions per the advisory are affected).
  3. Verify WLAN interface is present and enabled
    Check for active wireless interfaces using 'ip link show' or 'iwconfig'. Look for interfaces named wlan*, wl*, or similar wireless adapters.
    Affected if A WLAN interface exists and is configured, meaning the vulnerable code path could be triggered.
  4. Check for recent firmware update capability
    Examine whether the device firmware can be queried for version information. Some devices expose this via UEFI/BIOS interfaces, bootloader output, or vendor-specific tools. Look for 'fw_printenv' or vendor diagnostic interfaces.
    Affected if Firmware version cannot be verified as updated, or the device is running original vendor firmware from before the CVE disclosure date (2019).

A defender is affected if their device uses one of the listed Qualcomm chipsets (IPQ8074, MDM9206, MDM9207C, MDM9607, QCN7605, SM8150) and has WLAN functionality enabled with unpatched firmware.

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

Obtain and deploy patched WLAN firmware updates from Qualcomm for affected chip generations (IPQ8074, MDM9206, MDM9207C, MDM9607, QCN7605, SM8150). Coordinate with downstream device manufacturers to ensure firmware propagation.

Fix this in Ipq8074 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
92.0 hours of engineering $16,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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