CVE-2020-11304
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 · uneditedPossible out of bound read in DRM due to improper buffer length check. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
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 confidenceAn out-of-bounds read vulnerability exists in the DRM component of Qualcomm Snapdragon chipsets due to insufficient buffer length validation. The improper check allows reading memory beyond allocated buffer boundaries, potentially exposing sensitive data. This affects multiple Snapdragon product lines spanning mobile, automotive, IoT, compute, and infrastructure 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 chipset modelCheck the processor/SoC information in the device system information or via terminal command such as 'cat /proc/cpuinfo' on Android, or check the hardware specifications in the system BIOS or device manager.Affected if The chipset model matches Apq8009, Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, or Csrb31024.
-
Confirm the DRM subsystem is activeCheck if the Digital Rights Management (DRM) subsystem or Widevine/PlayReady content protection is enabled and running on the device. This can be verified through DRM service logs, system service status, or DRM info APIs available in the OS.Affected if The DRM component is loaded and actively processing content, exposing the vulnerability window.
-
Inspect firmware version informationQuery the baseband or system firmware version through device diagnostics, engineering mode, or AT command interface (for mobile modems). The firmware version is typically found in settings under 'About phone' > 'Baseband version' or via terminal commands.Affected if The device is running any firmware version on an affected chipset, as all versions are vulnerable.
The environment is affected if the device uses any of the listed Qualcomm chipset models (Apq8009, Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024) and the DRM subsystem is active and processing 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-supplied firmware updates from Qualcomm for affected Snapdragon chipsets. Device manufacturers must integrate these updates and deploy to end-user devices. Until patches are available, monitor for anomalous DRM behavior and restrict untrusted content processing.
- Consultation8.0 h
- Testing16.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 $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11304 — 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-11304 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