CVE-2020-11243
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 · uneditedRRC sends a connection establishment success to NAS even though connection setup validation returns failure and leads to denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile
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 confidenceRRC (Radio Resource Control) layer in Qualcomm Snapdragon chipsets incorrectly sends a connection establishment success message to NAS (Non-Access Stratum) even when connection setup validation has failed. This protocol logic error causes a state mismatch that leads to denial of service.
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, baseband info, or system diagnostics to determine the exact Qualcomm modem or chipset model (e.g., Aqt1000, Ar8035, Fsm10055, Fsm10056, Pm3003a, Pm7150a, Pm7150l, Pm7250)Affected if The chipset model matches any of the affected models listed in the CVE (Aqt1000, Ar8035, Fsm10055, Fsm10056, Pm3003a, Pm7150a, Pm7150l, Pm7250)
-
Check baseband firmware versionView the baseband or modem firmware version in device settings (typically under Settings > About Phone > SIM Status, or via AT commands such as AT+CGMR, or through system diagnostic tools)Affected if The device runs any firmware version on an affected chipset - the CVE states all versions are affected
-
Verify cellular radio functionality is enabledConfirm that cellular/Radio Resource Control (RRC) connections are active on the device - check if the device has cellular service capability and is attempting or maintaining mobile network connectionsAffected if Cellular RRC/NAS functionality is present and active on the device with an affected chipset
-
Monitor for connection anomaliesReview system logs, modem logs, or network diagnostic data for patterns indicating RRC/NAS state mismatch - look for repeated connection failures, unexpected connection success messages followed by immediate drops, or NAS layer errors during cellular attachment/establishmentAffected if Logs show connection establishment success messages delivered to NAS when validation should have failed, or unusual patterns of connection failures that could indicate this protocol state mismatch issue
The device is affected if it contains any of the listed Qualcomm chipsets (Aqt1000, Ar8035, Fsm10055, Fsm10056, Pm3003a, Pm7150a, Pm7150l, Pm7250) with cellular functionality enabled, since all firmware versions of these chipsets are vulnerable to the RRC/NAS state mismatch 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 dataThis is a firmware/baseband processor vulnerability requiring a patch from Qualcomm and deployment through OEM device updates. Network operators may implementworkarounds such as enhanced monitoring or traffic filtering to mitigate impact until firmware updates are available.
- Consultation8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11243 — 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-11243 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