CVE-2022-33279
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 · uneditedMemory corruption due to stack based buffer overflow in WLAN having invalid WNM frame length.
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 stack-based buffer overflow vulnerability exists in the WLAN component's WNM (Wireless Network Management) frame processing. When handling an invalid WNM frame with a malformed length field, the vulnerability allows memory corruption due to insufficient bounds checking before copying data onto the stack. This can be exploited remotely via specially crafted wireless frames.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 wireless chipset modelCheck the hardware specifications, boot logs, or system files (e.g., lspci, lsusb, or device tree) to determine if the device uses one of the affected Qualcomm chipsets: Ar9380, Csr8811, Ipq4019, Ipq4028, Ipq4029, Ipq5010, Ipq5018, or Ipq5028Affected if The device contains any of the listed Qualcomm chipsets (Ar9380, Csr8811, Ipq4019, Ipq4028, Ipq4029, Ipq5010, Ipq5018, Ipq5028)
-
Verify WNM feature statusCheck the wireless interface configuration for WNM (Wireless Network Management) support. On Linux, use 'iw list' or 'iw dev <interface> info' to examine supported features and configurations. Look for 'WNM' or 'Wireless Network Management' in the outputAffected if WNM features are listed as supported or enabled on the wireless interface
-
Confirm WNM processing is activeExamine running wireless interfaces and determine if they are operating in a mode (AP, mesh, or client) that processes incoming WNM frames. Check interface configuration files or use 'iwconfig' or 'ip link show' to confirm the interface is active and in a mode that accepts wireless management framesAffected if The wireless interface is active and configured to process 802.11 management frames including WNM
-
Review firmware versionQuery the wireless firmware or driver version via system logs, debug interfaces, or vendor tools. Commands like 'dmesg | grep -i firmware', 'cat /sys/class/net/*/device/firmware_version', or vendor-specific utilities may reveal the installed firmware versionAffected if The firmware version matches any of the affected Qualcomm chipsets listed, regardless of specific version number
A device is affected if it uses any of the listed Qualcomm chipsets (Ar9380, Csr8811, Ipq4019, Ipq4028, Ipq4029, Ipq5010, Ipq5018, Ipq5028) and has WNM feature processing enabled on its wireless interface.
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-specific patches for affected WLAN firmware/driver components. Until a patch is available, consider network segmentation to limit exposure of affected wireless devices and disable WNM features if not required.
- Consultation3.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 $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33279 — 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-33279 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