CVE-2020-11157
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 · uneditedu'Lack of handling unexpected control messages while encryption was in progress can terminate the connection and thus leading to a DoS' in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8053, APQ8076, MDM9640, MDM9650, MSM8905, MSM8917, MSM8937, MSM8940, MSM8953, QCA6174A, QCA9886, QCM2150, QM215, SDM429, SDM439, SDM450, SDM632
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 denial of service vulnerability in Qualcomm Snapdragon chipsets where unexpected control messages received during active encryption handshakes cause the connection to terminate unexpectedly. This affects WiFi/connectivity functionality in the baseband firmware.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Qualcomm chipset modelCheck device specifications, packaging, or use AT command 'AT+CGMM' (for baseband) or system info to query the chipset. On Android, check Settings > About Phone > Chipset or baseband version.Affected if The chipset is one of: Apq8053, Apq8076, Mdm9640, Mdm9650, Msm8905, Msm8917, Msm8937, or Msm8940
-
Confirm baseband firmware versionQuery the baseband firmware version using AT command 'AT+CGMR' or through Android settings under Settings > About Phone > Baseband version.Affected if Any firmware version is installed on the affected chipsets (all versions are vulnerable)
-
Verify WiFi or connectivity functionality is in useCheck if the device uses WiFi or cellular connectivity features. This vulnerability affects the baseband WiFi/connectivity subsystem.Affected if The device actively uses WiFi or cellular connectivity modules which handle encryption handshakes
-
Check for unexpected connection terminationsReview system logs, network connection logs, or dmesg for repeated connection drops, handshake failures, or baseband crash indications during active network sessions.Affected if Connections terminate unexpectedly during encryption handshakes without other explaiable cause
A user is affected if their device contains any of the listed Qualcomm chipsets (Apq8053, Apq8076, Mdm9640, Mdm9650, Msm8905, Msm8917, Msm8937, Msm8940) and uses WiFi or cellular connectivity, as all firmware versions for these chipsets are vulnerable to the denial of service flaw.
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 dataContact device OEMs and Qualcomm for available firmware updates; inventory affected devices and apply patches when released. Network-level mitigations like rate limiting may reduce exploitability but do not resolve the underlying firmware flaw.
- Consultation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,384.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11157 — 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-11157 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