CVE-2022-33271
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 · uneditedInformation disclosure due to buffer over-read in WLAN while parsing NMF 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 buffer over-read vulnerability in the WLAN component allows information disclosure when parsing Network Management Frame (NMF) data. This occurs when the parser reads beyond the allocated buffer boundaries, potentially exposing sensitive memory contents to an attacker who can send malformed NMF 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 model in your deviceCheck the device specifications, hardware documentation, or use commands like 'lspci', 'iw list', or 'cat /proc/net/wireless' to identify the Qualcomm wireless chip installedAffected if The chipset matches any of: Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, or Csra6640
-
Confirm WLAN functionality is enabledCheck if the wireless interface is up using 'ip link show' or 'iwconfig' commands. Verify the WLAN driver is loaded and the interface existsAffected if The WLAN interface is active or can be activated, meaning the vulnerable WLAN component is present and operational
-
Verify Network Management Frame parsing is activeConfirm the device is capable of processing management frames. This is typically inherent to normal WLAN operation - check if the device accepts or processes wireless association requestsAffected if The device processes or can process NMF frames, which is standard behavior for any functioning WLAN device with these chipsets
-
Check firmware version if accessibleUse vendor-specific tools or check /etc/firmware, /lib/firmware, or similar paths for the Qualcomm firmware files. Some devices may expose version via 'dmesg' or 'firmware_info' commandsAffected if Firmware version is readable and matches one of the affected chipset models (note: all versions of these chips are affected)
Your environment is affected if you use any of the listed Qualcomm chipsets (Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640) with WLAN functionality enabled, since all firmware versions of these chips 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 patches for affected WLAN devices. If no patch is available, consider network segmentation to limit exposure of vulnerable wireless components.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33271 — 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-33271 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