CVE-2021-30344
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 · uneditedImproper authorization of a replayed LTE security mode command can lead to a denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial 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 · moderate confidenceA vulnerability in Qualcomm Snapdragon chipsets allows an attacker to replay LTE security mode commands without proper authorization validation. The LTE security mode command is meant to establish encryption and integrity protection between the device and network, but the replayed command is not properly checked, enabling a remote attacker to cause a denial of service by disrupting LTE connectivity.
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 device chipset modelCheck the device specifications, manual, or use AT command 'AT+CGMM' or 'AT+GMM' to query the modem chipset modelAffected if The chipset model matches any of these: Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar6003, Ar8035, or Csrb31024
-
Verify the chipset is from Qualcomm Snapdragon familyConfirm the device uses a Qualcomm Snapdragon or Qualcomm cellular chipset by reviewing device documentation or system informationAffected if The device uses a Qualcomm Snapdragon or related chipset for LTE connectivity
-
Confirm LTE capability is presentVerify the device supports LTE/4G by checking network capabilities or using 'AT+CPSI?' to query system informationAffected if The device has LTE capability and uses one of the affected chipsets
-
Check if baseband firmware version is accessibleUse AT commands such as 'AT+CGMR' or 'AT+CGMM' to retrieve baseband firmware version information from the modemAffected if The baseband firmware is from Qualcomm and the chipset is on the affected list (all versions are vulnerable)
If the device contains any of the listed Qualcomm chipsets (Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar6003, Ar8035, or Csrb31024) and supports LTE, the device is affected since all firmware versions are vulnerable.
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 vulnerability requires a firmware update from Qualcomm and subsequent deployment by device manufacturers. Users should monitor for and apply security updates from their device vendors as they become available.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30344 — 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-2021-30344 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