CVE-2019-14030
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 · uneditedThe size of a buffer is determined by addition and multiplications operations that have the potential to overflow due to lack of bound check in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in MDM9205, QCS404, Rennell, SC8180X, SDM845, SDM850, SDX55, SM6150, SM7150, SM8150, SM8250, 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 · moderate confidenceInteger overflow vulnerability in buffer size calculation within Qualcomm Snapdragon chipsets. The buffer size is determined by addition and multiplication operations without proper bounds checking, allowing the computed size to overflow and result in an undersized buffer allocation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelCheck device documentation, boot logs, or use system commands such as 'cat /proc/cpuinfo' on Linux, 'lscpu', or check AT command responses for modem devices. For mobile devices, check /sys/devices/soc0/soc_id or /proc/device-tree/compatible.Affected if The chipset model matches any of the following: Mdm9205, Qcs404, Rennell, Sc8180x, Sdm845, Sdm850, Sdx55, or Sm6150.
-
Determine the firmware versionQuery the firmware version through vendor-specific methods: AT commands for modems (e.g., 'AT+CGMR' or 'AT+GMR'), boot logs, or system information APIs. Consult device/vendor documentation for the correct method.Affected if A firmware version is returned (indicating the chipset is present).
-
Verify the vulnerability scopeSince the advisory lists all versions as affected for each chipset, cross-reference the identified chipset and firmware version against the affected product list.Affected if The chipset is confirmed as one of the eight affected models.
-
Check for reachable vulnerable code pathIdentify which subsystem or feature on the device performs buffer size calculations (such as media processing, data parsing, or network handling). Consult vendor documentation to determine if the specific component using the vulnerable buffer calculation is present and active on the device.Affected if The device implements the subsystem containing the vulnerable buffer size calculation logic.
The device is affected if it contains any of the eight listed Qualcomm chipset models (Mdm9205, Qcs404, Rennell, Sc8180x, Sdm845, Sdm850, Sdx55, Sm6150) regardless of firmware version, since all versions are listed as affected.
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 dataApply vendor firmware patches from Qualcomm/OEMs for affected Snapdragon chipsets. Until patches are available, minimize exposure by restricting network access to affected devices and monitoring for exploitation.
- Consultation16.0 h
- Implementation24.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 $18,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14030 — 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-14030 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