CVE-2020-11189
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 Qualcomm Snapdragon chipsets where SDP (Session Description Protocol) values are parsed without proper NULL termination validation. When received SDP data lacks a NULL terminator, the parsing logic can read beyond the buffer boundary, potentially allowing memory disclosure or 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
- 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 affected Qualcomm chipset models in your environmentInventory all network devices, IoT devices, or embedded systems and verify if they contain any of these Snapdragon APQ variants: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8084, Apq8096au, or Aqt1000. Consult device documentation, hardware specifications, or use commands like 'lspci', 'cat /proc/cpuinfo', or vendor-specific tools to identify chipset models.Affected if Any device in the environment uses one of the listed Qualcomm APQ chipset models
-
Verify SDP parsing functionality is enabledCheck device firmware or application configuration to determine whether Session Description Protocol (SDP) parsing or SDP handling features are actively used. This may involve reviewing running services, SIP/VoIP configurations, WebRTC settings, or media server configurations depending on the device type.Affected if SDP parsing or SDP handling features are enabled and actively processing SDP data
-
Inspect network traffic for SDP contentUse packet capture tools (such as tcpdump, Wireshark, or network taps) to monitor incoming and outgoing network traffic for SDP messages. SDP messages typically begin with 'v=', 'o=', 's=', 'c=' lines and are commonly carried over SIP (port 5060), WebRTC (DTLS/SRTP), or RTP/RTSP sessions.Affected if SDP traffic is being transmitted to or from affected devices
-
Review device firmware versionAccess the firmware or boot loader information on the Qualcomm Snapdragon device and record the firmware version. Consult device vendor documentation for the specific command or method (often via AT commands, debug UART, or proprietary management interfaces).Affected if The device firmware corresponds to any of the affected Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8084, Apq8096au, or Aqt1000 chipset variants, regardless of version number
You are affected if your environment contains any device using the listed Qualcomm Snapdragon APQ chipset models and that device has SDP parsing functionality enabled and processing 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 updates for affected Snapdragon products. Until patches are available, limit exposure by ensuring SDP traffic originates from trusted sources and implementing network-level filtering of SDP traffic.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11189 — 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-11189 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