CVE-2024-21459
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 handling beacon or probe response frame in STA.
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 vulnerability in the Wi-Fi station (STA) mode allows an attacker within radio range to trigger information disclosure by sending specially crafted beacon or probe response frames. The issue is in how the wireless stack processes these management frames, potentially exposing sensitive memory contents to an unauthenticated remote attacker.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the Qualcomm Wi-Fi chip or platform modelCheck the device specifications, system information, or Wi-Fi adapter details to determine if the hardware uses one of the affected chipsets: Snapdragon W5+ Gen 1, Snapdragon 870 (sm8250 Ac), Snapdragon 865+ (sm8250 Ab), Wsa8835, Wsa8830, Wsa8815, Wsa8810, or Wcn3988. This may be listed in /proc/cpuinfo, device manager, or product documentation.Affected if The device contains any of the listed affected Qualcomm chipsets/firmware variants
-
Confirm Wi-Fi is operating in Station (STA) modeCheck the current Wi-Fi mode configuration. On Linux, use 'iwconfig' or 'iw dev' to see if the interface is in managed/STA mode. On Android, check via 'settings global wifi_country_code' or in Wi-Fi advanced settings. Verify the device is connected to an access point rather than acting as an access point itself.Affected if Wi-Fi interface is configured in Station (STA) or Managed mode and actively connected or scanning for access points
-
Check the installed firmware versionRetrieve the Wi-Fi firmware version from the device. On Linux, check /lib/firmware/ or use 'dmesg | grep firmware'. On Android, use 'getprop' or check in About Phone > Wi-Fi Chipset info. Compare against the affected product list - note that all versions of the listed firmware are affected.Affected if The device runs any firmware version on the listed affected platforms (all versions are vulnerable)
-
Verify if vendor security patches have been appliedCheck for available firmware or driver updates from the device vendor. On Linux, review changelogs or security advisories for the Wi-Fi driver/firmware. On Android, check System Updates or Security Patch level in Settings. Contact the device manufacturer or refer to their security advisory pages.Affected if No vendor firmware or driver security patches for CVE-2024-21459 have been applied, or the vendor has not released a patch for the specific platform
A user is affected if their device contains any of the listed Qualcomm Wi-Fi chipsets (W5+ Gen 1, Snapdragon 870/865+, Wsa8835/8830/8815/8810, Wcn3988) and has Wi-Fi STA mode enabled, without vendor-supplied security patches for this CVE.
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/driver patches for affected Wi-Fi devices operating in STA mode. Until patches are available, limit exposure by ensuring only trusted access points are connected to and monitor for anomalous probe responses.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21459 — 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-21459 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