dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14076

HIGH · 7.8 CVSS v3.1 Published 2020-06-22
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
Buffer overflow occurs while processing an subsample data length out of range due to lack of user input validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8098, Kamorta, MDM9150, MDM9205, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8998, Nicobar, QCS404, QCS405, QCS605, Rennell, SA415M, SC7180, SC8180X, SDA845, SDM670, SDM710, SDM845, SDM850, 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 · moderate confidence

A buffer overflow vulnerability exists in Snapdragon chipsets where processing subsample data occurs without validating that the data length falls within acceptable bounds. The lack of user input validation on the subsample data length allows an attacker to trigger the overflow, potentially leading to code execution or denial of service.

MitigationImplement proper input validation to verify subsample data length is within expected ranges before processing. This firmware-level fix requires a patch from Qualcomm distributed through OEM device updates.

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
Apq8098 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9205 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 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 processor/chipset information on the device. On Android, this may be found in /proc/cpuinfo, under Settings > About Phone > Chipset, or via commands like 'cat /sys/devices/soc0/family' or 'cat /sys/devices/soc0/machine'. On embedded devices, check the hardware specifications or boot logs for the Qualcomm Snapdragon model number.
    Affected if The chipset matches one of the affected models: Apq8009, Apq8098, Kamorta, Mdm9150, Mdm9205, Mdm9206, Mdm9607, or Mdm9650
  2. Confirm firmware version
    Retrieve the firmware or baseband version. On Android, check Settings > About Phone > Baseband version, or use 'getprop ro.baseband' via ADB shell. For other embedded platforms, check the firmware version through the bootloader, NV partition, or manufacturer documentation.
    Affected if Any firmware version is present on an affected chipset, as all versions are vulnerable
  3. Identify subsample processing feature
    Determine if the device processes subsample data in multimedia or baseband processing. This is typically a firmware-level function in the Snapdragon processor related to video/audio codec processing or baseband data handling. Check if the device uses Qualcomm's multimedia or baseband subsystems.
    Affected if The device utilizes the vulnerable subsample processing code path within the Snapdragon firmware

A device is affected if it contains any of the listed Qualcomm chipsets (Apq8009, Apq8098, Kamorta, Mdm9150, Mdm9205, Mdm9206, Mdm9607, Mdm9650) with firmware that includes the subsample data processing functionality.

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 input validation to verify subsample data length is within expected ranges before processing. This firmware-level fix requires a patch from Qualcomm distributed through OEM device updates.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing32.0 h
  • Review / QA12.0 h
100.0 hours of engineering $17,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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