dbcve.org
Msm8909w FirmwareOperating system · Qualcomm

CVE-2019-10495

HIGH · 7.3 CVSS v3.1 Published 2019-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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
Arbitrary buffer write issue while processing sequence header during HEVC or AVC encoding. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, Snapdragon_High_Med_2016, SXR1130

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 chipsets allowing arbitrary memory writes during HEVC/AVC video encoding sequence header processing. The flaw permits write operations beyond buffer boundaries, potentially enabling code execution or denial of service.

MitigationApply Qualcomm firmware/security updates provided by device OEMs. No workarounds available; users must wait for patched firmware releases from original equipment manufacturers.

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
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qualcomm 215 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 425 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 in your device
    Check device specifications, FCC ID filings, or system information to determine the Qualcomm Snapdragon chipset model. This is often listed in device specs under 'processor' or 'chipset'.
    Affected if The chipset model is Msm8909w, Msm8996au, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, or Sd 425.
  2. Confirm HEVC/AVC video encoding is in use
    Determine whether the device or application uses HEVC (H.265) or AVC (H.264) video encoding. This may be visible in video recording settings, media player info, or active video processing pipelines.
    Affected if HEVC or AVC video encoding features are enabled or actively used on the device.
  3. Check if the device uses the affected video encoder component
    Review the video encoding software stack or firmware to confirm the vulnerable Qualcomm video encoder component is present and active. This may require examining system logs, vendor documentation, or security assessment tools.
    Affected if The Qualcomm video encoder processing sequence headers is present and operational on the device.
  4. Review firmware version for patch status
    Check the current firmware version of the Qualcomm chipset. Note that all versions of the listed products are affected, but confirming the version helps document the exposure.
    Affected if The firmware version cannot be determined or no security patch for CVE-2019-10495 has been applied.

A device is affected if it contains one of the listed Qualcomm chipsets (Msm8909w, Msm8996au, Qcs605, Qualcomm 215, Sd 210, Sd 212, Sd 205, or Sd 425) and uses HEVC/AVC video encoding functionality, since all firmware versions of these products contain the vulnerability.

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

Apply Qualcomm firmware/security updates provided by device OEMs. No workarounds available; users must wait for patched firmware releases from original equipment manufacturers.

Fix this in Msm8909w Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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