CVE-2021-1937
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 · uneditedReachable assertion is possible while processing peer association WLAN message from host and nonstandard incoming packet in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, 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 · moderate confidenceA reachable assertion vulnerability exists in the WLAN peer association processing component of multiple Qualcomm Snapdragon chipset families. An attacker can trigger a denial of service by sending a specially crafted nonstandard packet during WLAN peer association from the host, causing an assertion failure and system crash.
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 modelExamine the device hardware specifications, bootloader information, or system logs to determine the exact Qualcomm chipset (e.g., Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024)Affected if The chipset matches any of the listed affected models (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024)
-
Check WLAN firmware versionQuery the WLAN firmware version through the device management interface, AT commands, or by reading firmware version registers via debug interfacesAffected if The WLAN firmware is running on an affected chipset and the version cannot be determined or is prior to a vendor patch
-
Verify WLAN peer association is enabledCheck device configuration settings or network status to confirm that WLAN functionality and peer association features are activeAffected if WLAN is enabled and the device participates in WLAN peer associations
-
Review system logs for assertion failuresExamine system crash logs, kernel logs, or firmware debug logs for messages indicating assertion failures or unexpected WLAN peer association crashesAffected if Logs show assertion failures or crashes during WLAN peer association processing
-
Inspect network exposureDetermine if the device WLAN interface is accessible to untrusted networks or attackers who could send crafted packets during the association phaseAffected if The WLAN interface is exposed to untrusted or unmanaged network segments
The device is affected if it uses any of the listed Qualcomm chipset families (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024) for WLAN and has WLAN peer association functionality enabled, regardless of firmware version since all 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 dataApply vendor-provided firmware patches from Qualcomm for affected Snapdragon devices. Until patches are available, consider network-level filtering of malformed WLAN association packets at access points or gateways.
- Consultation8.0 h
- Implementation4.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1937 — 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-1937 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