An update of the wpa_supplicant package has been released.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0716-1 advisory.

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

  - 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 access patterns. NOTE: this issue exists because of an     incomplete fix for CVE-2019-9495. (CVE-2022-23304)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of wpa_supplicant installed on the remote host is prior to 2.10 / 2.9. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2022-019-01 advisory.

  - The implementations of EAP-PWD in hostapd and wpa_supplicant are vulnerable to side-channel attacks as a     result of cache access patterns. All versions of hostapd and wpa_supplicant with EAP-PWD support are     vulnerable. The ability to install and execute applications is necessary for a successful attack. Memory     access patterns are visible in a shared cache. Weak passwords may be cracked. Versions of     hostapd/wpa_supplicant 2.7 and newer, are not vulnerable to the timing attack described in CVE-2019-9494.
    Both hostapd with EAP-pwd support and wpa_supplicant with EAP-pwd support prior to and including version     2.7 are affected. (CVE-2019-9495)

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

  - 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 access patterns. NOTE: this issue exists because of an     incomplete fix for CVE-2019-9495. (CVE-2022-23304)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote host is affected by the vulnerability described in GLSA-202309-16 (wpa_supplicant, hostapd: Multiple Vulnerabilities)

  - In wpa_supplicant and hostapd 2.9, forging attacks may occur because AlgorithmIdentifier parameters are     mishandled in tls/pkcs1.c and tls/x509v3.c. (CVE-2021-30004)

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

  - 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 access patterns. NOTE: this issue exists because of an     incomplete fix for CVE-2019-9495. (CVE-2022-23304)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - wpa_supplicant: SAE side channel attacks as a result of cache access patterns (CVE-2022-23303)

  - The implementation of PEAP in wpa_supplicant through 2.10 allows authentication bypass. For a successful     attack, wpa_supplicant must be configured to not verify the network's TLS certificate during Phase 1     authentication, and an eap_peap_decrypt vulnerability can then be abused to skip Phase 2 authentication.
    The attack vector is sending an EAP-TLV Success packet instead of starting Phase 2. This allows an     adversary to impersonate Enterprise Wi-Fi networks. (CVE-2023-52160)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The remote SUSE Linux SLES12 / SLES_SAP12 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:0504-1 advisory.

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

  - 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 access patterns. NOTE: this issue exists because of an     incomplete fix for CVE-2019-9495. (CVE-2022-23304)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

According to the versions of the wpa_supplicant package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This plugin has been deprecated as it does not adhere to established standards for this style of check.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2022:0716-1 advisory.

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

  - 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 access patterns. NOTE: this issue exists because of an     incomplete fix for CVE-2019-9495. (CVE-2022-23304)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES12 / SLES_SAP12 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2022:1853-1 advisory.

  - Multiple integer overflows in the NDEF record parser in hostapd before 2.5 and wpa_supplicant before 2.5     allow remote attackers to cause a denial of service (process crash or infinite loop) via a large payload     length field value in an (1) WPS or (2) P2P NFC NDEF record, which triggers an out-of-bounds read.
    (CVE-2015-8041)

  - Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Pairwise Transient Key (PTK) Temporal     Key (TK) during the four-way handshake, allowing an attacker within radio range to replay, decrypt, or     spoof frames. (CVE-2017-13077)

  - Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group Temporal Key (GTK) during the     four-way handshake, allowing an attacker within radio range to replay frames from access points to     clients. (CVE-2017-13078)

  - Wi-Fi Protected Access (WPA and WPA2) that supports IEEE 802.11w allows reinstallation of the Integrity     Group Temporal Key (IGTK) during the four-way handshake, allowing an attacker within radio range to spoof     frames from access points to clients. (CVE-2017-13079)

  - Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group Temporal Key (GTK) during the     group key handshake, allowing an attacker within radio range to replay frames from access points to     clients. (CVE-2017-13080)

  - Wi-Fi Protected Access (WPA and WPA2) that supports IEEE 802.11w allows reinstallation of the Integrity     Group Temporal Key (IGTK) during the group key handshake, allowing an attacker within radio range to spoof     frames from access points to clients. (CVE-2017-13081)

  - Wi-Fi Protected Access (WPA and WPA2) that supports IEEE 802.11r allows reinstallation of the Pairwise     Transient Key (PTK) Temporal Key (TK) during the fast BSS transmission (FT) handshake, allowing an     attacker within radio range to replay, decrypt, or spoof frames. (CVE-2017-13082)

  - Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Tunneled Direct-Link Setup (TDLS) Peer     Key (TPK) during the TDLS handshake, allowing an attacker within radio range to replay, decrypt, or spoof     frames. (CVE-2017-13086)

  - Wi-Fi Protected Access (WPA and WPA2) that support 802.11v allows reinstallation of the Group Temporal Key     (GTK) when processing a Wireless Network Management (WNM) Sleep Mode Response frame, allowing an attacker     within radio range to replay frames from access points to clients. (CVE-2017-13087)

  - Wi-Fi Protected Access (WPA and WPA2) that support 802.11v allows reinstallation of the Integrity Group     Temporal Key (IGTK) when processing a Wireless Network Management (WNM) Sleep Mode Response frame,     allowing an attacker within radio range to replay frames from access points to clients. (CVE-2017-13088)

  - An issue was discovered in rsn_supp/wpa.c in wpa_supplicant 2.0 through 2.6. Under certain conditions, the     integrity of EAPOL-Key messages is not checked, leading to a decryption oracle. An attacker within range     of the Access Point and client can abuse the vulnerability to recover sensitive information.
    (CVE-2018-14526)

  - The EAP-pwd implementation in hostapd (EAP server) before 2.8 and wpa_supplicant (EAP peer) before 2.8     does not validate fragmentation reassembly state properly for a case where an unexpected fragment could be     received. This could result in process termination due to a NULL pointer dereference (denial of service).
    This affects eap_server/eap_server_pwd.c and eap_peer/eap_pwd.c. (CVE-2019-11555)

  - The implementations of SAE and EAP-pwd in hostapd and wpa_supplicant 2.x through 2.8 are vulnerable to     side-channel attacks as a result of observable timing differences and cache access patterns when Brainpool     curves are used. An attacker may be able to gain leaked information from a side-channel attack that can be     used for full password recovery. (CVE-2019-13377)

  - The implementations of SAE in hostapd and wpa_supplicant are vulnerable to side channel attacks as a     result of observable timing differences and cache access patterns. An attacker may be able to gain leaked     information from a side channel attack that can be used for full password recovery. Both hostapd with SAE     support and wpa_supplicant with SAE support prior to and including version 2.7 are affected.
    (CVE-2019-9494)

  - The implementations of EAP-PWD in hostapd and wpa_supplicant are vulnerable to side-channel attacks as a     result of cache access patterns. All versions of hostapd and wpa_supplicant with EAP-PWD support are     vulnerable. The ability to install and execute applications is necessary for a successful attack. Memory     access patterns are visible in a shared cache. Weak passwords may be cracked. Versions of     hostapd/wpa_supplicant 2.7 and newer, are not vulnerable to the timing attack described in CVE-2019-9494.
    Both hostapd with EAP-pwd support and wpa_supplicant with EAP-pwd support prior to and including version     2.7 are affected. (CVE-2019-9495)

  - The implementations of EAP-PWD in hostapd EAP Server and wpa_supplicant EAP Peer do not validate the     scalar and element values in EAP-pwd-Commit. This vulnerability may allow an attacker to complete EAP-PWD     authentication without knowing the password. However, unless the crypto library does not implement     additional checks for the EC point, the attacker will not be able to derive the session key or complete     the key exchange. Both hostapd with SAE support and wpa_supplicant with SAE support prior to and including     version 2.4 are affected. Both hostapd with EAP-pwd support and wpa_supplicant with EAP-pwd support prior     to and including version 2.7 are affected. (CVE-2019-9497)

  - The implementations of EAP-PWD in hostapd EAP Server, when built against a crypto library missing explicit     validation on imported elements, do not validate the scalar and element values in EAP-pwd-Commit. An     attacker may be able to use invalid scalar/element values to complete authentication, gaining session key     and network access without needing or learning the password. Both hostapd with SAE support and     wpa_supplicant with SAE support prior to and including version 2.4 are affected. Both hostapd with EAP-pwd     support and wpa_supplicant with EAP-pwd support prior to and including version 2.7 are affected.
    (CVE-2019-9498)

  - The implementations of EAP-PWD in wpa_supplicant EAP Peer, when built against a crypto library missing     explicit validation on imported elements, do not validate the scalar and element values in EAP-pwd-Commit.
    An attacker may complete authentication, session key and control of the data connection with a client.
    Both hostapd with SAE support and wpa_supplicant with SAE support prior to and including version 2.4 are     affected. Both hostapd with EAP-pwd support and wpa_supplicant with EAP-pwd support prior to and including     version 2.7 are affected. (CVE-2019-9499)

  - 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 patterns. NOTE: this issue exists because of an incomplete fix     for CVE-2019-9494. (CVE-2022-23303)

  - 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 access patterns. NOTE: this issue exists because of an     incomplete fix for CVE-2019-9495. (CVE-2022-23304)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
203223	Photon OS 4.0: Wpa_Supplicant PHSA-2022-4.0-0153	Nessus	PhotonOS Local Security Checks	7/23/2024	7/23/2024	critical
158607	SUSE SLED15 / SLES15 Security Update : wpa_supplicant (SUSE-SU-2022:0716-1)	Nessus	SuSE Local Security Checks	3/5/2022	7/14/2023	critical
156857	Slackware Linux 14.0 / 14.1 / 14.2 / current wpa_supplicant Multiple Vulnerabilities (SSA:2022-019-01)	Nessus	Slackware Local Security Checks	1/19/2022	1/25/2022	critical
182401	GLSA-202309-16 : wpa_supplicant, hostapd: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	9/30/2023	9/30/2023	critical
199294	RHEL 8 : wpa_supplicant (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	6/3/2024	6/3/2024	critical
158182	SUSE SLES12 Security Update : wpa_supplicant (SUSE-SU-2022:0504-1)	Nessus	SuSE Local Security Checks	2/19/2022	7/13/2023	critical
203997	Photon OS 3.0: Wpa_Supplicant PHSA-2022-3.0-0358	Nessus	PhotonOS Local Security Checks	7/24/2024	7/24/2024	critical
161540	EulerOS 2.0 SP3 : wpa_supplicant (EulerOS-SA-2022-1771)	Nessus	Huawei Local Security Checks	5/26/2022	5/26/2022	critical
196855	RHEL 6 : wpa_supplicant (Unpatched Vulnerability) (deprecated)	Nessus	Red Hat Local Security Checks	5/11/2024	5/31/2024	critical
158625	openSUSE 15 Security Update : wpa_supplicant (openSUSE-SU-2022:0716-1)	Nessus	SuSE Local Security Checks	3/5/2022	3/5/2022	critical
161651	SUSE SLES12 Security Update : wpa_supplicant (SUSE-SU-2022:1853-1)	Nessus	SuSE Local Security Checks	5/28/2022	7/14/2023	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical