CVE-2024-33070
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 ESP IE from beacon/probe response 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 denial of service vulnerability exists in wireless device firmware where parsing an ESP (Encapsulating Security Payload) Information Element from beacon or probe response frames can cause a transient crash or hang. The vulnerability likely stems from insufficient bounds checking or improper validation of the ESP IE data during frame processing.
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 identifier (e.g., via lspci, lsusb, or /proc/bus/pci/devices for embedded adapters; for IoT/embedded devices, check the board documentation or /sys/class/net/*/device/uevent)Affected if The chipset matches one of: Qca6574au, Qca6574a, Qca6564au, Qca6564a, or Mdm9628
-
Verify firmware versionRetrieve the installed firmware version string (e.g., via iw, ethtool, device sysfs, or manufacturer diagnostic interface). For Qualcomm chipsets, check via 'iw list' or the firmware file name in /lib/firmware or /etc/wireless-regdb/Affected if The device is running firmware on any of the affected Qualcomm chipsets listed (all versions are vulnerable)
-
Confirm wireless interface is activeCheck if a wireless interface exists and is up (ip link show, iw dev, or similar)Affected if A wireless interface using the affected chipset is enabled and capable of receiving 802.11 beacon or probe response frames
-
Check ESP IE processing capabilityInspect whether the wireless driver/firmware has ESP IE parsing enabled (this is typically implicit in beacon/probe response processing; no specific toggle is user-configurable in most cases)Affected if The wireless interface processes incoming beacon or probe response frames, which triggers ESP IE parsing in the firmware
The environment is affected if it uses any of the listed Qualcomm chipsets (Qca6574au, Qca6574a, Qca6564au, Qca6564a, Mdm9628) with an active wireless interface that can receive beacon or probe response 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 dataApply vendor-supplied firmware updates when available. If no update exists, consider network segmentation to limit exposure to untrusted wireless networks and implement monitoring for anomalous beacon/probe response frames.
- 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-2024-33070 — 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-33070 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