CVE-2020-11299
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 · uneditedBuffer overflow can occur in video while playing the non-standard clip in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
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 · moderate confidenceBuffer overflow vulnerability in the video playback component of Qualcomm Snapdragon chipsets across multiple product lines (Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Mobile, Voice & Music, Wearables). The overflow occurs when processing a specially crafted non-standard video clip, potentially allowing arbitrary code execution.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Snapdragon chipset modelCheck the device hardware specifications, system information, or /proc/cpuinfo to determine the exact Qualcomm Snapdragon chipset model in useAffected if The chipset model matches one of the affected variants: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8064au, Apq8096au, Aqt1000, or Ar8031
-
Verify the firmware versionRetrieve the firmware version from the device settings, system firmware information, or by querying the baseband/ modem version via AT commands or diagnostic toolsAffected if The firmware version corresponds to any version of the affected chipset models listed (all versions are affected)
-
Confirm video playback capability is presentCheck if the device has video playback functionality enabled - verify video codecs and multimedia components are installed and active on the systemAffected if Video playback capability is present and enabled on a device using an affected Snapdragon chipset
-
Assess exposure to untrusted video sourcesReview the device or application configuration to determine if it can process video from external or untrusted sources (such as video players, messaging apps, or web browsers that handle video content)Affected if The device can process video from untrusted or non-standard video sources using the affected video playback component
A device is affected if it uses any of the listed Snapdragon chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8031) with video playback functionality enabled and potential exposure to untrusted video content.
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 vendor-provided security patches for affected Snapdragon devices; until patches are available, avoid playing video from untrusted sources.
- Consultation12.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,632.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11299 — 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-2020-11299 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