CVE-2024-33071
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 IE length is 0.
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 MBSSID (Multi-BSSID) Information Elements from beacon frames. When an MBSSID IE with a length of 0 is received, the parsing routine fails to handle this edge case properly, causing a transient DOS condition.
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 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 chipset modelCheck the system's wireless hardware specifications, lspci output for WiFi adapters, or device tree for embedded systems to identify the chipset vendor and modelAffected if The chipset is one of: Mdm9628, Qca6564a, Qca6564au, Qca6574a, or Qca6574au from Qualcomm
-
Verify MBSSID IE processing is enabledCheck wireless configuration settings for MBSSID support (also called Multi-BSSID or 11ax MBSSID). On APs, this is often found in beacon/SSID configuration optionsAffected if MBSSID feature is enabled and the device actively parses beacon frame IEs from neighboring APs
-
Confirm device role processes external beacon framesDetermine if the device operates as a client, repeater, or mesh node that receives and parses beacon frames from other APs (as opposed to only transmitting its own beacons)Affected if Device actively parses incoming beacon frames containing MBSSID IEs from other sources
-
Check firmware version if accessibleQuery the wireless firmware version through vendor tools (like iw, ath10k-util, or manufacturer-specific CLIs) or review firmware file metadataAffected if Any firmware version is present on the listed affected chipsets (all versions are vulnerable)
You are affected if your environment contains any of the listed Qualcomm chipsets (Mdm9628, Qca6564a, Qca6564au, Qca6574a, Qca6574au) and processes MBSSID Information Elements from beacon frames.
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 length validation for MBSSID IE before parsing; reject or skip zero-length IEs to prevent the parsing failure. Apply vendor patches when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33071 — 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-33071 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