CVE-2023-33097
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 Firmware while processing a FTMR frame.
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 high-severity denial-of-service vulnerability exists in WLAN firmware where processing a specially crafted Fast BSS Transition (FTMR) frame causes a transient DOS condition. The vulnerability is remotely exploitable without authentication, likely due to insufficient validation or error handling in the FTMR parsing logic.
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 hardware vendor and modelExamine the device specifications, label, or management interface to determine if the wireless chipset is a Qualcomm product from the affected list (Ar8035, Csr8811, Fastconnect 6900, Fastconnect 7800, Immersive Home 214/216/316/318)Affected if The device uses any of the listed Qualcomm firmware products
-
Check firmware versionAccess the wireless device management interface or use command-line tools (e.g., 'wl -iv', 'iw dev', or vendor-specific CLI) to retrieve the installed firmware versionAffected if The firmware version matches any of the affected products regardless of version number (all versions are affected)
-
Verify Fast BSS Transition (802.11r) is enabledCheck the wireless access point or client configuration for 802.11r (Fast BSS Transition) settings. This can be done via the management GUI under wireless security settings, or via CLI commands like 'iw list' or vendor-specific tools to query FTMR capability/enablement statusAffected if 802.11r Fast BSS Transition is enabled and the device processes FTMR frames
-
Review wireless traffic for FTMR framesMonitor wireless traffic using packet capture tools (e.g., Wireshark, tcpdump) filtering for 802.11 action frames with FTMR (Fast BSS Transition) action category and subtypeAffected if The device is actively receiving or processing Fast BSS Transition (FTMR) frames from unauthenticated sources
You are affected if your wireless device runs any version of the listed Qualcomm firmware products (Ar8035, Csr8811, Fastconnect 6900/7800, or Immersive Home 214/216/316/318) and has Fast BSS Transition (802.11r) enabled, as the vulnerability allows remote unauthenticated attackers to trigger a denial-of-service via crafted FTMR frames.
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 updates for affected wireless devices. Until patches are available, consider network segmentation to limit exposure of vulnerable wireless infrastructure.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33097 — 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-33097 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