LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24586: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privac...

The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances, when another device sends fragmented frames encrypted using WEP, CCMP, or GCMP, this can be abused to inject arbitrary network packets and/or exfiltrate user data.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-24586 is a Wi-Fi standards issue in how fragmented frames are handled after reconnecting. In specific wireless conditions, stale fragments may remain in memory and be misused to inject packets or expose user data. It affects behavior underpinning WEP, WPA, WPA2, and WPA3, so exposure depends on each vendor implementation and update status.

Executive priority

Handle through the wireless patch and asset-risk program. The issue is broad at the standards layer, but the available evidence does not prove active exploitation. Prioritize environments with sensitive Wi-Fi traffic, older devices, or difficult firmware management.

Technical view

The 802.11 standard does not require clearing received fragments from memory after reconnecting. Under the right conditions, fragmented frames encrypted with WEP, CCMP, or GCMP can be abused for packet injection or data exfiltration. Public references place this within the FragAttacks disclosure set and vendor-specific advisories.

Likely exposure

Organizations with Wi-Fi clients, access points, or firmware covered by Intel, Cisco, Arista, Debian, or other vendor guidance may be exposed. The bundle does not provide a precise affected product list, so validation must be vendor- and asset-specific.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. Abuse appears to require wireless proximity and specific fragmented-frame conditions. Treat it as a realistic local wireless risk, not confirmed internet-scale exploitation.

Researcher notes

Evidence is strongest for the protocol behavior and vendor advisory trail, but incomplete for exact product coverage in this bundle. Avoid assuming all Wi-Fi devices are equally affected; correlate by implementation, firmware lineage, and vendor fix status.

Mitigation direction

  • Review vendor advisories for each wireless chipset, access point, client, and operating system.
  • Apply relevant firmware, driver, kernel, or package security updates from trusted vendors.
  • Prioritize networks carrying sensitive traffic or supporting unmanaged wireless clients.
  • Retire or isolate devices that cannot receive vendor fixes.
  • Maintain strong application-layer encryption for sensitive services over Wi-Fi.

Validation and detection

  • Inventory wireless access points, clients, chipsets, drivers, firmware, and Linux kernel packages.
  • Map assets against Intel, Cisco, Arista, Debian, and applicable vendor advisories.
  • Verify installed firmware and package versions include the referenced security updates.
  • Check vulnerability scanner findings for FragAttacks or CVE-2020-24586 coverage.
  • Confirm compensating controls for unpatchable wireless devices are documented.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-24586 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.