Bugs fixes in "wpa"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-23304 | The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache acce | 2025-03-04 |
| CVE | CVE-2022-23303 | The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache access p | 2025-03-04 |
| CVE | CVE-2022-2330 | Improper Restriction of XML External Entity Reference vulnerability in DLP Endpoint for Windows prior to 11.9.100 allows a remote attacker to cause t | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-23304 | The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache acce | 2025-03-04 |
| CVE | CVE-2022-23303 | The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache access p | 2025-03-04 |
| CVE | CVE-2022-2330 | Improper Restriction of XML External Entity Reference vulnerability in DLP Endpoint for Windows prior to 11.9.100 allows a remote attacker to cause t | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-04 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-03 |
| CVE | CVE-2022-23304 | The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache acce | 2025-03-03 |
| CVE | CVE-2022-23303 | The implementations of SAE in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side channel attacks as a result of cache access p | 2025-03-03 |
| CVE | CVE-2022-2330 | Improper Restriction of XML External Entity Reference vulnerability in DLP Endpoint for Windows prior to 11.9.100 allows a remote attacker to cause t | 2025-03-03 |
| CVE | CVE-2022-37660 | In hostapd 2.10 and earlier, the PKEX code remains active even after a successful PKEX association. An attacker that successfully bootstrapped public | 2025-03-03 |
| CVE | CVE-2022-23304 | The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache acce | 2025-03-03 |
About
-
Send Feedback to @ubuntu_updates
