dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-2300

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 handler due to lack of validation of destination buffer size before copying into it 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, APQ8098, IPQ8074, MDM9206, MDM9207C, MDM9607, MSM8996, MSM8996AU, MSM8998, QCA6174A, QCA6574AU, QCA8081, QCA9377, QCA9379, QCA9886, QCS605, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, 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

Buffer overflow vulnerability in the WLAN handler component of Qualcomm Snapdragon chipsets caused by insufficient validation of destination buffer size before memory copy operations, potentially allowing remote code execution or denial of service attacks.

MitigationApply vendor firmware patches from device manufacturers as they become available; until then, implement network segmentation and access controls to limit exposure to WLAN attack vectors.

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
Apq8096 FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c 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 specifications or system information to determine the Qualcomm chipset model (e.g., via 'lspci', 'dmesg', device documentation, or manufacturer specs)
    Affected if The chipset is not one of the listed affected models (Apq8009, Apq8017, Apq8053, Apq8096, Apq8098, Ipq8074, Mdm9206, Mdm9207c)
  2. Confirm WLAN component is present
    Verify the device has WLAN capability by checking for wireless interfaces (e.g., 'ip link show', 'iwconfig', or hardware specifications)
    Affected if The device has no WLAN hardware or the WLAN module is physically not present
  3. Check if WLAN is enabled
    Verify the WLAN interface status via 'ip link show' or similar network tools to see if the wireless interface is up
    Affected if WLAN is enabled and the chipset is one of the affected models
  4. Determine firmware version
    Query the WLAN firmware version through driver interfaces (e.g., 'cat /sys/class/net/*/device/firmware_version', 'dmesg | grep firmware', or vendor-specific tools)
    Affected if The chipset matches an affected model and WLAN is enabled (all versions of listed models are affected)
  5. Verify WLAN handler is active
    Check that the WLAN handler/service is running (e.g., 'ps aux | grep wlan', 'systemctl status wpa_supplicant', or check network manager status)
    Affected if WLAN handler is active and the chipset is in the affected list

If the device uses any of the affected Qualcomm chipset models (Apq8009, Apq8017, Apq8053, Apq8096, Apq8098, Ipq8074, Mdm9206, Mdm9207c) and has WLAN enabled, the environment 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 device manufacturers as they become available; until then, implement network segmentation and access controls to limit exposure to WLAN attack vectors.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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