LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24588: 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 the A-MSDU flag in the plaintext QoS header field is authenticated. Against devices that support receiving non-SSP A-MSDU frames (which is mandatory as part of 802.11n), an adversary can abuse this to inject arbitrary network packets.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a Wi-Fi protocol weakness in how some devices process aggregated frames. A nearby attacker on radio range may inject network packets if a device accepts the affected A-MSDU frame form. It is broad in concept, but exposure depends on specific Wi-Fi chipsets, drivers, firmware, and vendor fixes. Potential exposure is in Wi-Fi access points, clients, embedded devices, and industrial systems using affected 802.11 implementations. The provided CVE data does not identify a complete affected product list, so exposure must be checked against vendor advisories and installed firmware, driver, and OS versions. Prioritize assessment and patch tracking for wireless infrastructure and high-value wireless clients. The issue is not listed as actively exploited in the provided data, but it affects a foundational Wi-Fi behavior and may persist in older firmware or embedded systems. Mitigation focus: Review vendor advisories for every Wi-Fi chipset, driver, access point, and embedded platform in use.; Apply vendor-provided firmware, driver, kernel, or OS security updates where available.; Prioritize wireless infrastructure, high-value laptops, and operational technology with Wi-Fi connectivity..

Prepared

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-24588 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
12Source links

CVSS and timeline data

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

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.