CVE-2020-11171
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 can happen while parsing received SDP values due to lack of NULL termination check on SDP 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 multiple Qualcomm Snapdragon chipset families when parsing Session Description Protocol (SDP) values. The vulnerability stems from missing NULL termination checks during SDP parsing, which can cause the parser to read beyond buffer boundaries into adjacent memory, potentially exposing sensitive data.
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 specifications or system information to determine the exact Qualcomm Snapdragon chipset model (e.g., Apq8009, Apq8017, Apq8053, etc.)Affected if The chipset matches any of the following: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8096au, Aqt1000, or Ar6003
-
Verify firmware versionAccess the device firmware or system settings and check the installed firmware version against the affected product list provided in the CVEAffected if The device firmware is for any of the affected products listed (all versions of Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8096au, Aqt1000, Ar6003)
-
Check if SDP parsing is activeExamine the device configuration or running processes to determine if Session Description Protocol parsing is enabled. This is typically used for VoIP, WebRTC, or video conferencing features.Affected if SDP parsing functionality is present and the device processes SDP data from network sources
-
Assess SDP input exposureReview network configuration and access controls to determine whether the device can receive SDP data from untrusted or external sources (e.g., SIP signaling, WebRTC connections)Affected if The device accepts SDP input from untrusted or unauthenticated network sources without validation
A device is affected if it uses any of the listed Qualcomm Snapdragon chipset models (Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8096au, Aqt1000, Ar6003) and processes SDP data from network 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 vendor-provided firmware/security patches from Qualcomm and device manufacturers for affected Snapdragon-based products. Until patches are available, restrict untrusted SDP input sources and monitor for anomalous network behavior.
- 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-11171 — 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-11171 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