CVE-2019-2311
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 · uneditedPossible buffer overflow in WLAN handler due to lack of validation of destination buffer size before copying 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, APQ8096AU, APQ8098, IPQ8074, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8996, MSM8996AU, MSM8998, QCA6174A, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCA9886, QCS605, SA6155P, SDA660, SDA845, SDM630, SDM636, 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 confidenceA buffer overflow vulnerability exists in the WLAN handler component of multiple Qualcomm Snapdragon chipset families. The flaw stems from insufficient validation of destination buffer size before copying data, allowing an attacker to overflow the buffer and potentially execute arbitrary code. Given the CVSS 9.8 rating, this is likely exploitable remotely without user interaction, affecting wireless networking functions across mobile, IoT, automotive, and infrastructure platforms.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelRetrieve the chipset identifier from system documentation, device specifications, or by running diagnostic commands such as 'cat /proc/cpuinfo' on embedded Linux systems, or check the baseband/modem information via 'AT+QCFG=' or similar carrier commands on mobile devicesAffected if The chipset model matches Apq8009, Apq8017, Apq8096, Apq8096au, Apq8098, Ipq8074, Mdm9206, or Mdm9207c
-
Confirm WLAN component is presentVerify that the WLAN or wireless networking functionality is available on the device. This may be observable through network interface listings (e.g., 'ip link show' or 'iw dev'), wireless driver loaded, or documented wireless capabilities in the device specsAffected if WLAN interfaces or wireless networking drivers are present and loaded on the system
-
Verify firmware versionCheck the installed firmware version for the WLAN component or baseband firmware. On Linux-based systems this may be accessible via 'cat /sys/firmware/devicetree/base/model' or through vendor-specific diagnostic tools. On mobile devices, check baseband version under Settings > About Phone > Baseband versionAffected if Any firmware version is installed on one of the affected chipset models, since the advisory lists all versions as affected
-
Determine WLAN handler is activeConfirm the WLAN handler component is actively processing wireless traffic. This can be observed by monitoring wireless interface activity, checking WLAN service status, or verifying that wireless networking functions are operationalAffected if The WLAN handler component is enabled and processing wireless communications on the affected chipset
A device is affected if it contains any of the listed Qualcomm chipset models (Apq8009, Apq8017, Apq8096, Apq8096au, Apq8098, Ipq8074, Mdm9206, Mdm9207c) with WLAN functionality present, regardless of firmware version.
Generated from the published advisory. Verify against your own configuration.
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 dataThis is a firmware-level vulnerability requiring a patch from Qualcomm and subsequent OEM/firmware distribution to affected devices. No workarounds or configuration changes are available; organizations must inventory affected hardware and apply vendor updates when available.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-2311 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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