CVE-2024-33051
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 processing TIM IE from beacon frame as there is no check for IE length.
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 · high confidenceA vulnerability exists in wireless device firmware where the TIM (Traffic Indication Map) Information Element processing from incoming beacon frames lacks proper length validation. An attacker within radio range can transmit a malformed beacon frame with an improperly sized TIM IE to trigger a denial of service 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 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 device chipset modelExamine the wireless device or access point hardware specifications, boot logs, or management interface to determine the exact chipset or module in use (e.g., look for Qualcomm 315, 9206, Apq8017, Aqt1000, Ar8031, Ar8035, Csra6620, or Csra6640)Affected if The device uses any of the listed Qualcomm chipset models (315, 9206, Apq8017, Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640)
-
Confirm beacon frame processing is enabledCheck the wireless device configuration to verify it is accepting and processing beacon frames from other devices. This is typically enabled by default in client mode, monitor mode, or when operating as a repeater/mesh nodeAffected if The device processes incoming beacon frames from other wireless stations (this is the code path where the vulnerable TIM IE parsing occurs)
-
Check firmware version if accessibleAccess the device firmware version through CLI (e.g., 'iw', 'wlanconfig', or vendor-specific command), Web UI, or SNMP OID if available. Compare against any vendor release notesAffected if The firmware version matches one of the affected products and the device accepts beacon frames (note: all listed firmware versions are affected)
-
Review device logs for anomaliesExamine system logs, kernel messages, or wireless driver logs for any crash reports, firmware assert failures, or unexpected resets that may indicate exploitation of the TIM IE processing vulnerabilityAffected if Logs show unexplained wireless interface resets, firmware crashes, or denial of service events correlating with presence of unexpected beacon frames
You are affected if your wireless device or IoT module uses any of the listed Qualcomm chipsets and processes incoming beacon frames from other devices.
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-provided firmware patches that add bounds checking for the TIM IE length before processing. Until patched, consider disabling beacon processing or using network monitoring to detect anomalous beacon frames.
- Consultation4.0 h
- Implementation4.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33051 — 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-33051 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