dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2019-10541

CRITICAL · 9.8 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 →
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
Dereference on uninitialized buffer can happen when parsing FLV clip with corrupted codec specific data in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9206, MDM9607, MSM8909W, MSM8996AU, QCA6574AU, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 439 / SD 429, SD 450, SD 600, 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, SDA660, SDM439, SDM630, SDM660, SDX20

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

A memory corruption vulnerability exists in Qualcomm Snapdragon chipsets where dereferencing an uninitialized buffer occurs when parsing FLV video clips with corrupted codec specific data. This allows remote attackers to potentially execute arbitrary code via malicious media files.

MitigationApply firmware patches from Qualcomm and subsequent OTA updates from device manufacturers. Users should keep device firmware updated and avoid processing untrusted FLV media files until patches are applied.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Qcs405 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qualcomm 215 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 Qualcomm chipset model in your device
    On Android, check /proc/cpuinfo or use 'getprop' command to retrieve the hardware/soc information. On embedded Linux systems, check /proc/device-tree/compatible or examine boot logs for chipset identifiers such as Mdm9206, Mdm9607, Msm8909w, Msm8996au, Qca6574au, Qcs405, Qcs605, or Qualcomm 215.
    Affected if The chipset matches any of the following: Mdm9206, Mdm9607, Msm8909w, Msm8996au, Qca6574au, Qcs405, Qcs605, or Qualcomm 215
  2. Check the firmware version
    Retrieve the firmware version through device settings (Settings > About Phone > Build Number), via 'getprop' on Android, or by examining boot logs and /proc/version for the firmware build string.
    Affected if All firmware versions of the affected chipsets are vulnerable since the advisory lists 'all versions' for each product
  3. Verify if FLV media parsing capability exists
    Check for FLV codec support in the media framework. On Android, examine /system/etc/media_codecs.xml or /vendor/etc/media_codecs.xml for FLV or FLV1 entries. Also check if applications capable of playing FLV files are installed.
    Affected if FLV playback or processing functionality is present on the device
  4. Inspect media server or codec service logs for FLV handling
    Examine logcat logs (adb logcat) or system logs for any references to FLV parsing, FLV1 codec initialization, or video clip processing that may indicate the vulnerable code path is reachable.
    Affected if The device processes or attempts to process FLV video files

A device is affected if it contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Msm8909w, Msm8996au, Qca6574au, Qcs405, Qcs605, or Qualcomm 215) and has the capability to parse FLV media files, as the vulnerability is triggered when processing corrupted codec specific data within FLV clips.

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 firmware patches from Qualcomm and subsequent OTA updates from device manufacturers. Users should keep device firmware updated and avoid processing untrusted FLV media files until patches are applied.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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