CVE-2022-33306
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 processing an incoming management frame with incorrectly filled IEs.
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 subsystem when processing incoming management frames containing incorrectly formatted Information Elements (IEs). An attacker can craft a malicious management frame with malformed IEs to trigger the buffer over-read, causing a denial of service (transient/system crash). The issue stems from insufficient bounds checking when parsing variable-length IEs in wireless management 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
- 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 Qualcomm WLAN hardware in useReview network device inventories, access point specifications, or wireless adapter documentation to determine if the device uses a Qualcomm Atheros chipset (Ar8035, Ar9380, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, or Ipq6010). This may be listed on device datasheets, FCC filings, or obtained via commands like 'lspci' for PCIe cards or by checking router admin interfaces.Affected if The environment contains any of the listed Qualcomm chip models (Ar8035, Ar9380, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010) regardless of firmware version.
-
Verify wireless interface statusCheck if wireless interfaces are enabled and active on affected devices. On Linux, use 'ip link show' or 'iwconfig' to list wireless interfaces and their state. On router interfaces, check the wireless configuration page to confirm radios are enabled.Affected if A wireless interface is up and capable of receiving management frames, as the vulnerability is triggered by processing incoming malformed IEs in management frames.
-
Confirm firmware versionObtain the firmware version from the wireless device or access point. This may be available via the device admin interface (typically under Status or Wireless settings), via SNMP, or by logging into the device and checking 'dmesg' for firmware load messages, or using vendor-specific commands. Compare the version string against the affected product list.Affected if The device runs any firmware version on the listed Qualcomm platforms (all versions are affected).
-
Assess network exposureDetermine if wireless interfaces are exposed to untrusted networks. Check whether the wireless network is open, uses weak encryption, or is in a location where arbitrary actors could transmit management frames (such as public Wi-Fi, guest networks, or unconferenced corporate wireless).Affected if The wireless interface can receive management frames from untrusted sources, which is required to deliver the malicious malformed IEs.
A defender is affected if their environment contains any of the listed Qualcomm WLAN chipsets (Ar8035, Ar9380, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010) with an active wireless interface that can receive management frames, since all firmware versions of these products are vulnerable.
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 updates for affected WLAN devices. Until patches are available, consider network segmentation to limit exposure of vulnerable WLAN interfaces to untrusted networks and disable unused wireless interfaces.
- 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-33306 — 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-33306 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