CVE-2020-11192
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 · uneditedOut of bound write while parsing SDP string due to missing check on null termination 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 · high confidenceA buffer overflow vulnerability exists in the SDP (Session Description Protocol) parsing code of Qualcomm Snapdragon chipsets. The vulnerability is caused by a missing check for null termination when parsing SDP strings, leading to an out-of-bounds write that could allow remote 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 chipset modelOn Android devices, run 'cat /proc/cpuinfo' or check Settings > About Phone > Chipset/model information. On other embedded systems, check /proc/device-tree/compatible or use 'lspci'/'lsusb' for connected device info.Affected if The chipset model matches any of these: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8096au, Aqt1000, or Ar8035.
-
Check the firmware versionUse manufacturer-specific commands or tools to read the baseband processor or Wi-Fi firmware version. On Android, check Settings > About Phone > Build Number, or use 'getprop' commands. For IoT devices, consult the vendor's diagnostic interface.Affected if The firmware version is any version of the affected chipset listed above, since all versions are vulnerable.
-
Determine if SDP parsing is in useIdentify if the device supports VoIP, WebRTC, video calling, or any real-time communication features. Check running processes for SIP/SDP-related services, or monitor network traffic for SDP payloads (typically on ports 5060/5061 or WebRTC channels).Affected if SDP parsing is enabled and the device processes SDP messages from untrusted sources, which is common in any VoIP or WebRTC implementation on the affected chipsets.
-
Inspect SDP handling code pathsIf you have access to firmware binaries or debug logs, search for SDP parsing functions. On Android, check logcat for SDP-related errors or crashes. Review any custom SDP parsing implementations in vendor applications.Affected if The device exhibits crashes or unexpected behavior related to session description handling, which may indicate exploitation attempts.
A user is affected if their device contains any of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Aqt1000, Ar8035, or Apq8096au) and uses any SDP-dependent feature such as VoIP or video calling.
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 the vendor-provided patch from Qualcomm to the affected chipset firmware. For downstream devices, await and apply the firmware update from the device manufacturer. Until patched, minimize exposure by restricting network attack surface.
- Consultation4.0 h
- Implementation8.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11192 — 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-11192 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