CVE-2022-33285
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 while parsing WLAN CSA action frames.
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 buffer over-read vulnerability exists in the WLAN component when parsing WLAN Channel Switch Announcement (CSA) action frames. This can cause a transient denial of service by reading beyond the allocated buffer boundary during frame parsing.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 chipset modelCheck the device hardware specifications, bootloader, or system information to determine if the chipset is one of the following: Apq8009, Apq8017, Apq8064au, Apq8076, Apq8096au, Aqt1000, Ar8031, or Ar8035Affected if The device uses any of these Qualcomm chipsets
-
Check WLAN firmware versionQuery the WLAN driver or firmware version via commands such as 'iw list', 'wlan_tool version', or through the device's system information menuAffected if The WLAN firmware version corresponds to any of the affected chipset models listed above
-
Verify WLAN is enabledCheck if the WLAN interface is up and active using commands like 'ip link show', 'iw dev', or through the device's network settingsAffected if WLAN is enabled and actively processing frames
-
Inspect for CSA frame handlingExamine the WLAN driver configuration or capture network traffic to observe if Channel Switch Announcement (CSA) action frames are being processed. This can be done via packet capture tools or driver debug logsAffected if CSA action frames are being parsed by the WLAN component
-
Check for crash logs or buffer over-read indicatorsReview system logs (dmesg, kernel logs, or vendor-specific logs) for signs of crashes, buffer over-read errors, or unexpected WLAN resets, especially in relation to CSA frame processingAffected if Logs show crashes or errors during WLAN CSA frame parsing
If the device uses any of the listed Qualcomm chipsets and has WLAN enabled with CSA frame processing capability, the environment is likely affected by this buffer over-read 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/driver updates that address the buffer over-read in WLAN CSA action frame parsing. If updates are unavailable, consider network-level mitigations such as filtering untrusted CSA frames at access point level.
- Consultation4.0 h
- Implementation8.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33285 — 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-33285 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