dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14006

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-21
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
Buffer overflow occur while playing the clip which is nonstandard due to lack of offset length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8064, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996, MSM8996AU, Nicobar, QCS605, QM215, Rennell, SA6155P, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, 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 · high confidence

Buffer overflow vulnerability in Qualcomm Snapdragon chipset media playback functionality. The flaw stems from insufficient offset/length validation when processing non-standard video clips, allowing memory corruption that could enable remote code execution or denial of service.

MitigationApply vendor firmware/security patches from Qualcomm and device OEMs. Until patches are available, avoid playing media from untrusted sources.

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
Apq8064 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 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 processor model. Common methods include checking /proc/cpuinfo on Android devices, reviewing device documentation, or using system info apps.
    Affected if The chipset model matches one of the following: Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Apq8098, Mdm9206, Mdm9207c, or Mdm9207c.
  2. Verify the firmware version
    Query the firmware version of the Qualcomm component. On Android devices, this can often be found in Settings > About Phone > Build Number, or by checking the modem firmware version through AT commands (AT+CGMR) or diagnostic tools.
    Affected if The firmware version cannot be determined or exists on an affected chipset, since the advisory states all versions are affected.
  3. Confirm media playback functionality is present
    Determine if the device has video playback capabilities. Check if video player applications are installed or if the device supports multimedia processing. Review installed apps and system features related to media/camera/video.
    Affected if The device supports video playback or multimedia processing functionality.
  4. Assess exposure to untrusted media sources
    Evaluate whether the device can receive or play media from external or untrusted sources. This includes checking if the device supports sideloading apps, receiving video files via messaging apps, browsing the web, or connecting to untrusted networks for media streaming.
    Affected if The device can process video files from sources outside the trusted OEM supply chain, such as web downloads, messaging apps, or external storage.

If the device uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Apq8098, Mdm9206, Mdm9207c) and has media playback capability, it is likely affected since all firmware versions are vulnerable.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware/security patches from Qualcomm and device OEMs. Until patches are available, avoid playing media from untrusted sources.

Recommended fix Moderate confidence

Firmware update from device OEM (contact Qualcomm chipset customers/device OEMs for specific fixed firmware releases)

  1. Contact your device OEM (the manufacturer of the device using the affected Snapdragon chipset) to obtain firmware updates incorporating the CVE-2019-14006 fix
  2. Verify with the device OEM that the firmware update includes the security patch for the buffer overflow vulnerability in media clip processing
  3. Apply the OEM-provided firmware update through the manufacturer's recommended update process
  4. After updating, verify the patch was applied by checking the device firmware version matches the OEM's fixed release
Caveat Firmware updates may have compatibility implications; test thoroughly in a non-production environment before deploying widely

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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