CVE-2023-33105
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 · uneditedTransient DOS in WLAN Host and Firmware when large number of open authentication frames are sent with an invalid transaction sequence number.
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 in WLAN Host and Firmware where processing a large number of open authentication frames with invalid transaction sequence numbers causes a transient service disruption. The vulnerability lies in the WLAN authentication handling logic that fails to properly validate or throttle malformed authentication requests.
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 wireless chipset in useCheck system documentation, device inventory, or use commands like 'lspci -v' for PCIe wireless cards, 'lsusb' for USB adapters, or check router/mobile device specifications to identify the Qualcomm wireless chip model (Ar8035, Ar9380, Csr8811, Fastconnect 6700/6900/7800, Flight Rb5 5g, or Immersive Home 214)Affected if The device uses any of the affected Qualcomm chips listed in the CVE (Ar8035, Ar9380, Csr8811, Fastconnect 6700/6900/7800, Flight Rb5 5g, Immersive Home 214)
-
Check WLAN firmware versionAccess the device's firmware or system information (through router admin interface, 'iw version', 'wlanconfig', or device-specific diagnostic tools) to determine the installed WLAN firmware versionAffected if The firmware version matches any of the affected products (all versions of the listed Qualcomm firmware are affected)
-
Verify WLAN interface is activeCheck if WLAN interfaces are present and enabled using 'ip link show', 'iwconfig', 'rfkill list', or through the device's network management interfaceAffected if WLAN interfaces are active and the device uses an affected Qualcomm wireless chip
-
Check for authentication frame handlingMonitor WLAN traffic using packet capture tools (tcpdump, Wireshark) specifically watching for authentication frames (type=0, subtype=0x0B) to observe if the device processes incoming auth requestsAffected if The device's WLAN interface processes open authentication frames and the device uses affected Qualcomm firmware
-
Look for DoS exploitation indicatorsReview system logs, wireless access point logs, or network monitoring data for signs of authentication floods, service disruptions, or abnormal auth frame volumes. Check for 'authentication failed', 'association failed', or unexpected WLAN restartsAffected if Logs show repeated authentication failures, WLAN service interruptions, or abnormally high volumes of malformed authentication frames correlated with affected hardware
The environment is affected if any device uses the listed Qualcomm wireless chipsets (Ar8035, Ar9380, Csr8811, Fastconnect 6700/6900/7800, Flight Rb5 5g, Immersive Home 214) with WLAN functionality enabled, as all firmware versions of these products contain the 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-provided firmware/software updates for affected WLAN devices. Implement network-level rate limiting or traffic filtering for authentication frames as a compensating control until patches are available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33105 — 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-2023-33105 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