CVE-2024-33011
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 while parsing the MBSSID IE from the beacons, when the MBSSID IE length is zero.
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 denial of service vulnerability exists in the parsing logic for Multiple BSSID Information Elements (MBSSID IE) in wireless device firmware. When processing beacon frames containing an MBSSID IE with a zero-length value, the parser fails to handle this edge case properly, causing a transient crash or hang of the affected device.
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 wireless hardware in your environmentCheck device specifications, firmware inventory, or system logs to determine if any of the following Qualcomm chips are present: Wsa8845h, Wsa8845, Wsa8840, Wsa8835, Wsa8832, Wsa8830, Wsa8815, or Wsa8810Affected if Any of these eight Qualcomm WSA chip models are in use, as all versions are affected
-
Verify wireless firmware versionQuery the wireless device firmware version via vendor management interface, SNMP, or device console command (such as 'iw dev' or vendor-specific firmware dump)Affected if Firmware version matches any of the eight affected chip models regardless of version number, since all versions are vulnerable
-
Confirm MBSSID IE processing is activeCheck if the wireless device is operating as an access point, mesh node, or repeater that transmits or receives beacon frames. Monitor network traffic or check wireless configuration for Multiple BSSID supportAffected if Device processes beacon frames with MBSSID Information Elements, which triggers the vulnerable parsing code path
-
Inspect wireless configuration for MBSSID featureReview wireless interface configuration files or management settings for parameters related to MBSSID, multiple BSS support, or multi-AP configurationsAffected if MBSSID feature is enabled in the wireless configuration, making the device actively parse MBSSID IEs in incoming beacon frames
You are affected if your environment contains any of the eight listed Qualcomm WSA chips (Wsa8845h through Wsa8810) with wireless beacon frame processing enabled, regardless of firmware version.
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 dataImplement proper input validation to check MBSSID IE length before parsing; reject or skip zero-length MBSSID IEs to prevent the parsing routine from dereferencing invalid memory.
- Consultation4.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33011 — 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-2024-33011 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