CVE-2020-11283
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 · uneditedA buffer overflow can occur when playing an MKV clip due to lack of input validation 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 · high confidenceA buffer overflow vulnerability exists in Qualcomm Snapdragon chipsets due to insufficient input validation when parsing MKV video files. The lack of proper bounds checking during video playback allows an attacker to overwrite memory by crafting a malicious MKV file, potentially achieving remote 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 chipset modelDetermine the specific Qualcomm chipset model used in the device (e.g., through system information, device specifications, or /proc/cpuinfo on Linux-based embedded systems)Affected if The chipset matches any of these models: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8064au, Apq8096au, Aqt1000, or Ar8031
-
Confirm MKV playback capabilityCheck whether the device or software stack supports MKV video file decoding or has video playback libraries that handle MKV containersAffected if MKV video parsing or playback functionality is present and enabled on the system
-
Verify video processing componentsInspect installed video codecs, multimedia frameworks, or firmware modules related to video parsing (look for libavformat, ffmpeg, or vendor-specific video SDKs)Affected if Video parsing components that handle MKV containers are installed or loaded on the device
-
Assess exposure to untrusted contentDetermine whether the device can process MKV files from external sources, network streams, or untrusted input (e.g., media player apps, file browsers, video processing services)Affected if The device can parse or play MKV files from sources outside the trusted software supply chain
The device is affected if it uses any of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8031) and has MKV video playback capability enabled, making it vulnerable when processing malicious MKV files.
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-supplied firmware patches from Qualcomm and ensure device manufacturers' security updates are deployed. Until patches are available, avoid playing untrusted MKV files from unknown sources.
- Consultation8.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11283 — 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-11283 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