CVE-2024-33073
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 while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.
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 or similar parsing error in the Multi-Link Information Element (ML IE) processing code allows disclosure of information from memory when parsing the BSS parameter change count or MLD capabilities fields. The vulnerability exists in wireless firmware or driver code that handles 802.11be (Wi-Fi 7) ML IE parsing.
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
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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 wireless hardwareRun 'lspci | grep -i network' or 'lsusb' to list wireless adapters. Look for Qualcomm Atheros or Qualcomm identifiers in the WSA (Wi-Fi) or WCD (Wireless Communication Device) product families.Affected if The system contains a Qualcomm WSA8845h, WSA8845, WSA8840, WSA8835, WSA8832, WSA8830, WCD9395, or WCD9390 wireless chipset.
-
Check wireless driver and firmware versionRun 'iw list' or 'ethtool -i <interface>' to retrieve driver and firmware version information. On Android, check /vendor/firmware or use 'getprop' for radio versions.Affected if The driver reports a firmware version for any of the listed Qualcomm chipsets, indicating the vulnerable firmware code is in use.
-
Verify 802.11be (Wi-Fi 7) support is activeRun 'iw <interface> info' or 'iw list' to check the supported IEEE standards. Look for '802.11be' or 'EHT' (Extremely High Throughput) in the supported modes or bands.Affected if The wireless interface advertises 802.11be support, meaning ML IE parsing code is being executed.
-
Monitor for memory disclosure indicatorsCheck system logs with 'dmesg' or 'journalctl -b | grep -i wifi' for unusual wireless firmware messages, crashes, or unexpected behavior during association with Multi-Link devices.Affected if The system processes ML IE from Wi-Fi 7 (802.11be) access points or peer devices, which triggers the vulnerable parsing code path.
The system is affected if it uses any of the listed Qualcomm WSA or WCD wireless chipsets with 802.11be (Wi-Fi 7) enabled, as all firmware versions contain the vulnerable ML IE parsing code.
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 dataUpdate wireless device firmware or driver to a version containing the patch that properly validates bounds and restricts memory reads during ML IE field parsing.
- 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-2024-33073 — 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-33073 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