Ieee 802 11 Ieee 802 11

Do you want an email whenever new security vulnerabilities are reported in Ieee 802 11?

By the Year

In 2024 there have been 0 vulnerabilities in Ieee 802 11 . Last year Ieee 802 11 had 1 security vulnerability published. Right now, Ieee 802 11 is on track to have less security vulnerabilities in 2024 than it did last year.

Year Vulnerabilities Average Score
2024 0 0.00
2023 1 7.50
2022 0 0.00
2021 3 3.20
2020 0 0.00
2019 0 0.00
2018 0 0.00

It may take a day or so for new Ieee 802 11 vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Ieee 802 11 Security Vulnerabilities

The IEEE 802.11 specifications through 802.11ax

CVE-2022-47522 7.5 - High - April 15, 2023

The IEEE 802.11 specifications through 802.11ax allow physically proximate attackers to intercept (possibly cleartext) target-destined frames by spoofing a target's MAC address, sending Power Save frames to the access point, and then sending other frames to the access point (such as authentication frames or re-association frames) to remove the target's original security context. This behavior occurs because the specifications do not require an access point to purge its transmit queue before removing a client's pairwise encryption key.

Authentication Bypass by Spoofing

The 802.11 standard

CVE-2020-24588 3.5 - Low - May 11, 2021

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.

Use of a Broken or Risky Cryptographic Algorithm

The 802.11 standard

CVE-2020-24587 2.6 - Low - May 11, 2021

The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. An adversary can abuse this to decrypt selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP encryption key is periodically renewed.

Use of a Broken or Risky Cryptographic Algorithm

The 802.11 standard

CVE-2020-24586 3.5 - Low - May 11, 2021

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.

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Linux Kernel or by Ieee? Click the Watch button to subscribe.

Ieee
Vendor

Ieee 802 11
Product

subscribe