dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-14057

CRITICAL · 9.1 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 →
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 Over read of codec private data while parsing an mkv file due to lack of check of buffer size before read 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, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996, MSM8996AU, MSM8998, Nicobar, QCA6574AU, QCS405, QCS605, QM215, Rennell, SA6155P, Saipan, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, 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

Buffer over-read vulnerability in the mkv file parser's codec private data handling. The parser fails to validate buffer size before reading data, allowing an attacker to read beyond buffer boundaries by crafting a malicious mkv file with oversized codec private data.

MitigationApply Qualcomm firmware/security patches to affected devices. Since this is a chipset-level vulnerability in Snapdragon processors, remediation requires coordinated firmware updates from device manufacturers - there is no application-level workaround.

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Qualcomm chipset model
    Check device specifications or use system information commands (e.g., 'cat /proc/cpuinfo' on Android, or check BIOS/UEFI information) to determine the exact Snapdragon/Qualcomm processor model
    Affected if chipset model matches Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Mdm9206, or Mdm9207c
  2. Check the firmware version
    Retrieve the firmware version from the device. On Android devices, this may be available via 'getprop' commands, in system settings, or through the baseband version string (e.g., 'getprop ro.build.version.security_patch' or checking the modem firmware version)
    Affected if firmware version is any version prior to vendor-supplied security patches addressing CVE-2019-14057 (compare against vendor release notes)
  3. Determine if mkv parsing is accessible
    Identify whether the device has media playback capabilities that process mkv files. This may involve checking installed media players, video processing services, or codecs available on the system
    Affected if device can parse or play mkv media files using the affected chipset firmware
  4. Inspect media processing components
    Review any applications or services that handle video files. Check for presence of video players, media servers, or transcoding tools that process mkv container format
    Affected if mkv file handling functionality is present and uses the vulnerable codec private data parser in the firmware

Device is affected if it uses one of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Mdm9206, Mdm9207c) with any firmware version and has the capability to process mkv files through the vulnerable parser.

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 Qualcomm firmware/security patches to affected devices. Since this is a chipset-level vulnerability in Snapdragon processors, remediation requires coordinated firmware updates from device manufacturers - there is no application-level workaround.

Recommended fix Moderate confidence
  1. Contact your device OEM (Original Equipment Manufacturer) to obtain and apply the latest firmware update that includes the Qualcomm security patch addressing CVE-2019-14057
  2. Do not use the mkv file parsing functionality until the firmware update is applied
  3. Verify with your OEM that the patch containing the fix for buffer over-read in mkv codec private data parsing has been applied
  4. For embedded/IoT device integrators: contact Qualcomm for the BSP/firmware update containing the security fix
Caveat Firmware updates may require device downtime and should be tested in a staging environment before production deployment

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

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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 locally
dbcve dependency scanner

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