CVE-2022-33252
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 handling IBSS beacons 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 exists in the WLAN component when processing IBSS (Independent Basic Service Set) beacon frames, allowing an attacker within radio range to potentially read sensitive information from memory beyond the intended buffer boundaries.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 wireless hardware modelCheck the system hardware or wireless chipset documentation, BIOS/UEFI information, or OS network adapter details to determine the exact Qualcomm wireless chip modelAffected if The chip model matches any of: Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Ipq5010, Ipq5018, or Ipq5028
-
Check WLAN firmware versionQuery the wireless firmware version through the operating system's network diagnostics, device manager, or vendor-specific management toolsAffected if The firmware version is any version of the affected Qualcomm chips (all versions are vulnerable)
-
Verify WLAN component is activeConfirm the wireless network interface is enabled and operational using OS network status commands or management interfacesAffected if WLAN is powered on and the interface is active
-
Check IBSS mode configurationReview wireless network settings, configuration files, or management interfaces to determine if Independent Basic Service Set (IBSS/Ad-hoc) mode is enabled or has been usedAffected if IBSS (ad-hoc) mode is configured, enabled, or was recently active on the affected WLAN interface
A system is affected if it uses any of the listed Qualcomm wireless chips (Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Ipq5010, Ipq5018, Ipq5028) with WLAN enabled and IBSS beacon frame processing active.
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-supplied firmware/software patches for the WLAN component that address bounds checking in IBSS beacon frame handling.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33252 — 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-33252 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