CVE-2020-11285
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 over-read while unpacking the RTCP packet we may read extra byte if wrong length is provided in RTCP packets in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon 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 confidenceA buffer over-read vulnerability exists in the RTCP (Real-time Transport Control Protocol) packet unpacking functionality across multiple Qualcomm Snapdragon chipset families. When processing RTCP packets with a malformed or incorrect length field, the code may read beyond the allocated buffer boundary, potentially exposing sensitive memory contents to an attacker.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 device hardware specifications or system information to determine the Qualcomm Snapdragon APQ chipset model (e.g., APQ8009, APQ8017, APQ8053, etc.)Affected if The chipset is one of: APQ8009, APQ8009w, APQ8017, APQ8037, APQ8053, APQ8084, Aqt1000, or Apq8096au
-
Confirm firmware versionRetrieve the firmware version from the device's system settings, boot logs, or via AT command interface (for mobile devices). Compare against the affected product list.Affected if The firmware version corresponds to any of the listed affected products (all versions of each listed product are affected)
-
Verify RTCP functionality is activeCheck if the device is configured to process or route real-time media streams (VoIP, video conferencing, WebRTC applications) which would involve RTCP packet handling. Inspect active network processes or services that handle RTP/RTCP protocols.Affected if The device processes RTP/RTCP traffic, making the RTCP packet unpacking code reachable
-
Monitor for malformed RTCP packetsCapture network traffic on interfaces handling real-time media and inspect RTCP packets for anomalies in the length field or malformed packet structures. Use tools like Wireshark with RTP analysis plugins.Affected if Malformed RTCP packets with incorrect length fields are being processed by the device
-
Check for exposed sensitive memoryReview application and system logs for any indications of memory disclosure, unexpected memory reads, or crashes originating from RTCP processing components.Affected if Logs show anomalous memory access patterns or crashes during RTCP packet handling
The device is affected if it uses any of the listed Qualcomm APQ chipset models (all versions) and actively processes RTCP traffic, allowing malformed packets to trigger the buffer over-read in the RTCP unpacking code.
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/BIOS updates for affected Snapdragon devices. In the interim, network-level filtering of malformed RTCP packets may provide partial mitigation.
- Consultation4.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 $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11285 — 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-11285 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