CVE-2020-11182
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 heap overflow while parsing NAL header due to lack of check of length of data received from user in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
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 confidenceHeap overflow vulnerability in Snapdragon chipsets when parsing NAL (Network Abstraction Layer) headers. The vulnerability exists because the code does not validate the length of user-supplied data before copying it to a heap buffer, allowing an attacker to overflow adjacent memory and potentially achieve 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 Qualcomm chipset model in the deviceCheck system information or device specifications to determine if a Qualcomm Snapdragon chipset is present. Look for the specific chipset model number.Affected if The device uses a Qualcomm Snapdragon chipset that incorporates any of the affected firmware modules (Aqt1000, Pm3003a, Pm4125, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l).
-
Determine the firmware version of the power management chip or Aqt1000 moduleAccess the device's firmware or bootloader information through manufacturer diagnostic tools, FCC documents, or device-specific debugging interfaces to identify the installed firmware version.Affected if The firmware version matches any of the listed affected products (Aqt1000, Pm3003a, Pm4125, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l) at any version, as all versions are vulnerable.
-
Check if NAL header parsing is being performedInspect running processes or network traffic to determine if the device is processing Network Abstraction Layer (NAL) units, typically associated with H.264/H.265 video streaming or VoIP applications.Affected if The device parses NAL headers from untrusted sources (such as incoming video streams or network packets), which would trigger the vulnerable code path.
-
Verify the device processes video or multimedia streamsReview application logs, network activity, or system services to confirm whether the device handles video encoding/decoding, streaming media, or VoIP traffic.Affected if The device processes multimedia streams that involve NAL unit parsing, making it potentially exploitable through malicious media content.
A device is affected if it contains a Qualcomm chipset with any of the listed firmware modules (Aqt1000, Pm3003a, Pm4125, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l) and processes NAL header data from external sources.
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 firmware updates from device/OEM vendors once Qualcomm releases the patch. There is no user-level mitigation; this requires vendor-supplied firmware updates.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11182 — 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-11182 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