CVE-2019-10578
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 · uneditedNull pointer dereference can occur while parsing the clip which is nonstandard 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, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996, MSM8996AU, MSM8998, Nicobar, QCA6574AU, QCS605, QM215, Rennell, 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 confidenceA null pointer dereference vulnerability exists in the clip parsing functionality of Qualcomm Snapdragon processors. When parsing a non-standard or malformed media clip, the processor can encounter a null pointer that gets dereferenced, leading to a denial of service condition or potentially unpredictable behavior. The vulnerability affects multiple Snapdragon product lines across mobile, IoT, compute, automotive, and wearable platforms.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset model in your deviceOn Android devices, go to Settings > About Phone > Chipset/Processor, or use terminal command 'cat /proc/cpuinfo' to display processor information. Check device documentation or product specifications.Affected if The chipset matches one of the affected models: Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Apq8098, Mdm9206, or Mdm9207c
-
Confirm firmware versionOn Android, go to Settings > About Phone > Build Number or use 'getprop ro.build.version.security_patch' to check the Android security patch level. For direct modem firmware version, use 'getprop gsm.version.baseband' or check under Settings > About Phone > Baseband version.Affected if The device runs any firmware version on an affected chipset - the advisory lists 'all versions' as vulnerable, so if the chipset is in the affected list, no specific firmware version provides safety
-
Verify media clip parsing is accessibleThe vulnerability exists in the clip parsing functionality within the Snapdragon firmware. This functionality processes media clips through the baseband/modem processor. Check if your device has multimedia capabilities or media processing features enabled that handle media clips.Affected if The device has any media playback capabilities - the parsing occurs in the firmware's multimedia processing layer which is typically always active when media features exist
-
Check for available security updatesContact your device manufacturer or check their support website for the most recent firmware/security update available for your specific device model.Affected if No firmware security update addressing CVE-2019-10578 has been applied to your device model
If your device uses any of the listed Qualcomm chipset models (Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Apq8098, Mdm9206, Mdm9207c) and processes media clips, your environment is affected unless a vendor security patch has been applied.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Qualcomm firmware security patches (typically delivered through monthly platform security updates) and ensure device manufacturers' firmware updates are deployed. For IoT/embedded deployments, coordinate with device vendors to obtain and apply patched firmware. Users should apply available system updates from their device manufacturers.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10578 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10578 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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