CVE-2020-11274
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 · uneditedDenial of service in MODEM due to assert to the invalid configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, 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 confidenceA denial of service vulnerability exists in the MODEM component of Qualcomm Snapdragon chipsets (Auto, Compute, Connectivity, Consumer IOT, Industrial IOT, Mobile). The vulnerability is caused by an assertion failure when the modem processes an invalid configuration, leading to a crash or hang condition that renders the modem non-functional.
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 modem chipset modelCheck the device specifications or use diagnostic tools (like *#*#4636#*#* on Android, or manufacturer-specific tools) to query the modem/hardware details. Look for chipset identifiers: Aqt1000, Csrb31024, Fsm10055, Fsm10056, Pm3003a, Pm456, Pm6125, or Pm6150.Affected if The device uses any of the listed chipsets (Aqt1000, Csrb31024, Fsm10055, Fsm10056, Pm3003a, Pm456, Pm6125, Pm6150).
-
Determine the installed modem firmware versionQuery the modem firmware version through AT commands (AT+CGMR or ATI), through the device's baseband information in settings (Android: Settings > About Phone > Baseband), or via manufacturer diagnostic software.Affected if The firmware version cannot be determined or is present on an affected chipset (all versions of the listed firmware are affected).
-
Check for modem crash or hang symptomsObserve the device for sudden loss of cellular connectivity, inability to make/receive calls or use mobile data, or modem-related error messages. Use diagnostic logs or carrier-specific test modes to check modem status.Affected if The modem exhibits crash, hang, or non-responsive behavior, especially when processing configuration data.
A user is affected if their device contains one of the listed Qualcomm modem chipsets (Aqt1000, Csrb31024, Fsm10055, Fsm10056, Pm3003a, Pm456, Pm6125, Pm6150) and is running the vulnerable firmware, as indicated by modem crashes or hangs when processing invalid configuration.
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-supplied firmware patches from Qualcomm through device OEM channels. This is a firmware-level issue requiring updates to the modem baseband software; there are no user-configurable mitigations.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11274 — 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-11274 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