dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14060

HIGH · 7.8 CVSS v3.1 Published 2020-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Uninitialized stack data gets used If memory is not allocated for blob or if the allocated blob is less than the struct size required due to lack of check of return value for read or write blob in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8098, IPQ4019, IPQ6018, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCS405, QCS605, QM215, Rennell, SA6155P, Saipan, SC8180X, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SDX24, SDX55, 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

This is an uninitialized memory vulnerability in Qualcomm Snapdragon firmware where read/write blob operations lack proper memory allocation checks and return value validation. When memory is either not allocated for a blob or is insufficiently allocated for the required struct size, uninitialized stack data gets used, potentially exposing sensitive information or causing unexpected behavior.

MitigationImplement proper memory allocation validation and return value checking before blob read/write operations. Ensure the allocated blob buffer is sufficient for the required struct size, and validate all return values from memory allocation and I/O functions.

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
Apq8098 FirmwareOperating system
Affected:all versions
Ipq4019 FirmwareOperating system
Affected:all versions
Ipq6018 FirmwareOperating system
Affected:all versions
Ipq8064 FirmwareOperating system
Affected:all versions
Ipq8074 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the chipset model
    Check the system hardware or bootloader information to determine the Qualcomm Snapdragon or IPQ chipset (e.g., Apq8009, Apq8017, Apq8053, Apq8098, Ipq4019, Ipq6018, Ipq8064, Ipq8074)
    Affected if The chipset matches any of the affected models: Apq8009, Apq8017, Apq8053, Apq8098, Ipq4019, Ipq6018, Ipq8064, or Ipq8074
  2. Confirm firmware version
    Retrieve the firmware version from the device (via bootloader, /proc/version, or vendor-specific interface) and verify it is a version for any of the affected chipsets
    Affected if The device runs firmware built for any of the affected Qualcomm chipset models listed in the CVE
  3. Identify blob read/write operations
    Inspect the firmware or application code that interfaces with the firmware to determine if blob read or write operations are performed (check for blob handling functions or data structure operations)
    Affected if The system performs blob read/write operations that interact with the affected firmware layer
  4. Check for memory allocation validation
    Review the firmware or associated software stack to verify whether proper memory allocation checks and return value validation exist before blob operations
    Affected if Memory allocation for blobs is not validated or insufficient buffer sizes are used before blob read/write operations, leading to uninitialized stack data exposure

A device is affected if it uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8098, Ipq4019, Ipq6018, Ipq8064, Ipq8074) and performs blob read/write operations without proper memory allocation validation, as the firmware lacks these checks across all versions.

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

Implement proper memory allocation validation and return value checking before blob read/write operations. Ensure the allocated blob buffer is sufficient for the required struct size, and validate all return values from memory allocation and I/O functions.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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