CVE-2020-11191
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 read occurs while processing crafted SDP due to lack of check of null string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
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 confidenceAn out-of-bounds read vulnerability exists in Qualcomm Snapdragon processors when parsing Session Description Protocol (SDP) messages. The vulnerability stems from missing null-string validation during SDP processing, allowing a remote attacker to trigger memory corruption by sending specially crafted SDP data. This affects multiple Snapdragon product lines used in mobile devices, IoT, wearables, and infrastructure equipment.
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 processor modelCheck the device specifications or system information to determine the Qualcomm Snapdragon/APQ processor model number (e.g., Apq8009, Apq8053, etc.). On Linux devices, this may be found in /proc/cpuinfo or via 'lscpu' command.Affected if The processor model matches one of the following: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8084, Apq8096au, or Aqt1000
-
Check firmware versionRetrieve the current firmware version from the device system settings, boot logs, or via vendor-specific diagnostic tools. For embedded devices, this may be accessible through /proc/version, dmidecode, or manufacturer-specific interfaces.Affected if Any firmware version is installed on an affected processor model, as all versions of these products are vulnerable
-
Identify if SDP parsing is in useAudit running processes and services that handle SIP, WebRTC, VoIP, video conferencing, or multimedia streaming protocols. Check configuration files and active network services for SDP (Session Description Protocol) handling components.Affected if The device runs any service or application that processes SDP messages, as this is the attack surface for the vulnerability
-
Check network exposureReview firewall rules, networkACLs, and service bindings to determine if SDP-handling services are exposed to untrusted network sources. Examine whether the device accepts SDP data from external network endpoints.Affected if SDP-processing services are accessible from untrusted network sources or the public internet, enabling remote exploitation
A device is affected if it uses any of the listed Qualcomm APQ processors (Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8084, Apq8096au, or Aqt1000) and processes SDP messages from potentially untrusted 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 through device manufacturer update channels. Until patches are deployed, restrict exposure to untrusted SDP sources and network attack surfaces.
- Consultation8.0 h
- Implementation16.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11191 — 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-11191 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