Ieee

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any Ieee product.

RSS Feeds for Ieee security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in Ieee products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by Ieee Sorted by Most Security Vulnerabilities since 2018

Ieee 802 114 vulnerabilities

Ieee 802 24 vulnerabilities

By the Year

In 2026 there have been 0 vulnerabilities in Ieee. Ieee did not have any published security vulnerabilities last year.

Year	Vulnerabilities	Average Score
2026	0	0.00
2025	0	0.00
2024	0	0.00
2023	1	7.50
2022	4	4.70
2021	3	3.20
2020	0	0.00
2019	0	0.00
2018	7	0.00

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

Recent Ieee Security Vulnerabilities

CVE	Date	Vulnerability	Products
CVE-2022-47522	Apr 15, 2023	802.11ax MAC Spoofing Queue Bypass Allows Cleartext Intercept 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.	Ieee 802 11
CVE-2021-27862	Sep 27, 2022	IPv6 RA Guard bypass via LLC/SNAP header length attack Layer 2 network filtering capabilities such as IPv6 RA guard can be bypassed using LLC/SNAP headers with invalid length and Ethernet to Wifi frame conversion (and optionally VLAN0 headers).	Ieee 802 2
CVE-2021-27861	Sep 27, 2022	Linux Kernel RA Guard Bypass via LLC/SNAP Header Exploit Layer 2 network filtering capabilities such as IPv6 RA guard can be bypassed using LLC/SNAP headers with invalid length (and optionally VLAN0 headers)	Ieee 802 2
CVE-2021-27854	Sep 27, 2022	Layer 2 RA Guard Bypass using VLAN0/LLC/SNAP & Ethernet-Wifi Layer 2 network filtering capabilities such as IPv6 RA guard can be bypassed using combinations of VLAN 0 headers, LLC/SNAP headers, and converting frames from Ethernet to Wifi and its reverse.	Ieee 802 2
CVE-2021-27853	Sep 27, 2022	CVE-2021-27853: VLAN 0+LLC/SNAP bypass of IPv6 RA guard (Cisco IOS XE) Layer 2 network filtering capabilities such as IPv6 RA guard or ARP inspection can be bypassed using combinations of VLAN 0 headers and LLC/SNAP headers.	Ieee 802 2
CVE-2020-24588	May 11, 2021	The 802.11 standard 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.	Ieee 802 11
CVE-2020-24587	May 11, 2021	The 802.11 standard 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.	Ieee 802 11
CVE-2020-24586	May 11, 2021	The 802.11 standard 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.	Ieee 802 11
CVE-2017-13091	Jul 13, 2018	The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), as well as the management of access rights for such IP, including improperly specified padding in CBC mode The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), as well as the management of access rights for such IP, including improperly specified padding in CBC mode allows use of an EDA tool as a decryption oracle. The methods are flawed and, in the most egregious cases, enable attack vectors that allow recovery of the entire underlying plaintext IP. Implementations of IEEE P1735 may be weak to cryptographic attacks that allow an attacker to obtain plaintext intellectual property without the key, among other impacts.
CVE-2017-13092	Jul 13, 2018	The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), as well as the management of access rights for such IP, including improperly specified HDL syntax The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), as well as the management of access rights for such IP, including improperly specified HDL syntax allows use of an EDA tool as a decryption oracle. The methods are flawed and, in the most egregious cases, enable attack vectors that allow recovery of the entire underlying plaintext IP. Implementations of IEEE P1735 may be weak to cryptographic attacks that allow an attacker to obtain plaintext intellectual property without the key, among other impacts.