CVE-2021-30321
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 · uneditedPossible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity
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 buffer overflow vulnerability exists in the MBSSID (Multi-BSSID) scan Information Element parsing code of Qualcomm Snapdragon chipsets. The lack of proper parameter length validation during IE parsing allows an attacker to overflow buffers, potentially leading to remote code execution or 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the device hardware specifications or use commands like 'lspci', 'lsusb', or check /proc/cpuinfo to identify the Qualcomm wireless chipset (e.g., Aqt1000, Qca1062, Qca1064, Qca2066, Qca6320, Qca6391, Qca6420, Qca6430)Affected if The chipset is one of the listed affected models (Aqt1000, Qca1062, Qca1064, Qca2066, Qca6320, Qca6391, Qca6420, Qca6430)
-
Check the wireless firmware versionUse vendor-specific commands such as 'iw list', 'ath11k-firmware', or access the device's firmware information through /lib/firmware or the wireless driver debug interface to determine the installed firmware versionAffected if The firmware version falls within the affected product family (all versions of the listed chipsets are affected)
-
Verify MBSSID feature is enabledCheck wireless configuration settings or access point settings for Multi-BSSID (MBSSID) support - look for configurations like 'mssid_enable', 'multi_bssid', or verify multiple BSSIDs are configured on the deviceAffected if MBSSID functionality is enabled and the device is transmitting or receiving MBSSID scan Information Elements
-
Inspect network traffic for MBSSID IECapture wireless network traffic using tools like Wireshark or airmon-ng and inspect beacon frames, probe responses, or scan results for Multi-BSSID Information Elements (IE type 0xdd with vendor-specific content)Affected if MBSSID scan IEs are being processed by the affected chipset firmware
The environment is affected if the device uses a Qualcomm chipset from the affected list (Aqt1000, Qca1062, Qca1064, Qca2066, Qca6320, Qca6391, Qca6420, Qca6430) with any firmware version and has MBSSID feature enabled or is processing MBSSID scan Information Elements.
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 updates from Qualcomm and device manufacturers to implement proper parameter length validation in MBSSID scan IE parsing.
- 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-30321 — 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-30321 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