CVE-2022-33309
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 due to buffer over-read in WLAN Firmware while parsing secure FTMR frame with size lesser than 39 Bytes.
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 over-read vulnerability exists in the WLAN firmware when parsing secure FTMR (Fast BSS Transition Management) frames smaller than 39 bytes. This causes a transient denial of service condition, likely resulting in device crash or wireless connectivity interruption. The flaw stems from insufficient bounds checking before reading memory beyond the allocated buffer during FTMR frame processing.
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 WLAN chipset modelCheck the device specifications, FCC filings, or log output for the Wi-Fi chipset (e.g., via 'lspci' for PCIe cards, 'iw list' for wireless interfaces, or vendor documentation)Affected if The device uses a Qualcomm Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010, Ipq6018, or Ipq6028 chipset
-
Check the installed firmware versionQuery the wireless firmware version via device administration interface, vendor CLI, or 'ethtool -i' / 'iw' commands depending on device type; compare against vendor security advisories for patch statusAffected if The firmware version has not been updated to include the vendor security patch for CVE-2022-33309 (or vendor indicates no patch is available)
-
Verify if 802.11r Fast BSS Transition is enabledCheck wireless access point or router configuration for 802.11r, FT, or Fast Roaming settings; on Linux, use 'iw dev <interface> info' or check hostapd.conf for 'fast_bss_transition=1'Affected if 802.11r/Fast BSS Transition is enabled and the device processes FTMR frames as part of client roaming
A device is affected if it uses any of the listed Qualcomm chipsets with an unpatched firmware version AND has 802.11r (Fast BSS Transition) enabled, since the vulnerability triggers when parsing FTMR frames smaller than 39 bytes during roaming operations.
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 the vendor-provided firmware update for affected WLAN devices to patch the buffer over-read vulnerability. If no update is available, consider network segmentation or disabling 802.11r (Fast BSS Transition) features as a temporary workaround.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33309 — 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-2022-33309 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