CVE-2021-30302
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 authentication of EAP WAPI EAPOL frames from unauthenticated user can lead to information disclosure in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, 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 confidenceImproper authentication in the EAP WAPI EAPOL frame handling allows unauthenticated users to send these frames, bypassing the authentication checks and potentially exposing sensitive information. This is a protocol-level flaw in the wireless authentication mechanism affecting multiple Snapdragon product lines.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 wireless chipset or access point modelCheck the device specifications, kernel modules, or hardware documentation to determine the Qualcomm chipset in use (Aqt1000, Ar8035, Ar9380, Csr8811, Ipq4018, Ipq4028, Ipq4029, or Ipq5010)Affected if The device uses any of the listed Qualcomm chipsets (Aqt1000, Ar8035, Ar9380, Csr8811, Ipq4018, Ipq4028, Ipq4029, Ipq5010)
-
Verify firmware versionCheck the firmware version of the wireless device or access point using vendor tools, SNMP, or device management interfaceAffected if The firmware is any version of the listed affected products (all versions are vulnerable)
-
Confirm WAPI protocol is enabledCheck wireless configuration settings, security policies, or device management interface for WAPI (WLAN Authentication and Privacy Infrastructure) authentication methodAffected if WAPI authentication is enabled on the wireless network
-
Check EAPOL frame handling configurationInspect wireless interface settings, capture configuration, or security logs for EAPOL (Extensible Authentication Protocol over LAN) frame processingAffected if The device processes or handles EAPOL frames (which is standard for 802.1X wireless authentication)
If the device uses any of the affected Qualcomm chipsets (Aqt1000, Ar8035, Ar9380, Csr8811, Ipq4018, Ipq4028, Ipq4029, Ipq5010) with any firmware version and has WAPI authentication enabled, the environment is affected by this vulnerability.
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 and ensure affected devices receive updates. Until patches are available, implement network segmentation and restrict access to vulnerable wireless infrastructure to reduce exposure.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30302 — 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-30302 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