CVE-2022-33236
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 cipher suite info attributes. in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
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 firmware of Qualcomm Snapdragon chipsets when parsing cipher suite info attributes. This causes a transient denial of service condition. The vulnerability affects multiple Snapdragon product lines including Compute, Connectivity, Mobile, and Wired Infrastructure and Networking platforms.
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 Qualcomm chipset in useAccess the device firmware, bootloader, or network device management interface to retrieve the chipset model number. Common locations: `lspci`, `cat /proc/cpuinfo`, vendor-specific CLI commands, or device documentation.Affected if The chipset model matches one of the following: Ar8035, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010, or Ipq6018
-
Confirm WLAN firmware is present and activeCheck if the device has WLAN functionality enabled. This may be visible in the device's network interfaces (e.g., wireless adapters), system services, or firmware components listing.Affected if WLAN interfaces or wireless firmware modules are present and operational on the device
-
Determine if the device processes WPA/WPA2/WPA3 enterprise or cipher suite negotiationsMonitor or inspect wireless client association traffic, particularly 802.11 RSN (Robust Security Network) or WPA handshake frames that contain cipher suite selectors. Check wireless controller/AP logs or capture wireless management frames.Affected if The device participates in wireless network negotiations where cipher suite attributes are parsed by the affected WLAN firmware component
-
Check firmware version and vendor advisory statusQuery the installed firmware version through vendor tools, device CLI, or bootloader. Cross-reference with Qualcomm's advisory documentation for this CVE.Affected if The firmware version is among the listed affected products and no vendor patch has been applied
You are affected if your device uses any of the listed Qualcomm chipsets (Ar8035, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010, Ipq6018) with WLAN functionality enabled, as all firmware versions of these products contain the buffer over-read flaw in cipher suite parsing.
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-supplied firmware update from Qualcomm or downstream device manufacturers that addresses the buffer over-read in WLAN cipher suite parsing. Until patched, monitor for service disruptions in affected wireless components.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33236 — 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-33236 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