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.

An update of the wpa_supplicant package has been released.

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.

This update for wpa_supplicant fixes the following issues :

wpa_supplicant was updated to 2.9 release :

  - SAE changes

  - disable use of groups using Brainpool curves

  - improved protection against side channel attacks     [https://w1.fi/security/2019-6/]

  - EAP-pwd changes

  - disable use of groups using Brainpool curves

  - allow the set of groups to be configured     (eap_pwd_groups)

  - improved protection against side channel attacks     [https://w1.fi/security/2019-6/]

  - fixed FT-EAP initial mobility domain association using     PMKSA caching (disabled by default for backwards     compatibility; can be enabled with     ft_eap_pmksa_caching=1)

  - fixed a regression in OpenSSL 1.1+ engine loading

  - added validation of RSNE in (Re)Association Response     frames

  - fixed DPP bootstrapping URI parser of channel list

  - extended EAP-SIM/AKA fast re-authentication to allow use     with FILS

  - extended ca_cert_blob to support PEM format

  - improved robustness of P2P Action frame scheduling

  - added support for EAP-SIM/AKA using anonymous@realm     identity

  - fixed Hotspot 2.0 credential selection based on roaming     consortium to ignore credentials without a specific EAP     method

  - added experimental support for EAP-TEAP peer (RFC 7170)

  - added experimental support for EAP-TLS peer with TLS     v1.3

  - fixed a regression in WMM parameter configuration for a     TDLS peer

  - fixed a regression in operation with drivers that     offload 802.1X 4-way handshake

  - fixed an ECDH operation corner case with OpenSSL

  - SAE changes

  - added support for SAE Password Identifier

  - changed default configuration to enable only groups 19,     20, 21 (i.e., disable groups 25 and 26) and disable all     unsuitable groups completely based on REVmd changes

  - do not regenerate PWE unnecessarily when the AP uses the     anti-clogging token mechanisms

  - fixed some association cases where both SAE and FT-SAE     were enabled on both the station and the selected AP

  - started to prefer FT-SAE over SAE AKM if both are     enabled

  - started to prefer FT-SAE over FT-PSK if both are enabled

  - fixed FT-SAE when SAE PMKSA caching is used

  - reject use of unsuitable groups based on new     implementation guidance in REVmd (allow only FFC groups     with prime >= 3072 bits and ECC groups with prime >=     256)

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-1/]     (CVE-2019-9494, bsc#1131868)

  - EAP-pwd changes

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-2/]     (CVE-2019-9495, bsc#1131870)

  - verify server scalar/element     [https://w1.fi/security/2019-4/] (CVE-2019-9497,     CVE-2019-9498, CVE-2019-9499, bsc#1131874, bsc#1131872,     bsc#1131871, bsc#1131644)

  - fix message reassembly issue with unexpected fragment     [https://w1.fi/security/2019-5/] (CVE-2019-11555,     bsc#1133640)

  - enforce rand,mask generation rules more strictly

  - fix a memory leak in PWE derivation

  - disallow ECC groups with a prime under 256 bits (groups     25, 26, and 27)

  - SAE/EAP-pwd side-channel attack update     [https://w1.fi/security/2019-6/] (CVE-2019-13377,     bsc#1144443)

  - fixed CONFIG_IEEE80211R=y (FT) build without     CONFIG_FILS=y

  - Hotspot 2.0 changes

  - do not indicate release number that is higher than the     one AP supports

  - added support for release number 3

  - enable PMF automatically for network profiles created     from credentials

  - fixed OWE network profile saving

  - fixed DPP network profile saving

  - added support for RSN operating channel validation     (CONFIG_OCV=y and network profile parameter ocv=1)

  - added Multi-AP backhaul STA support

  - fixed build with LibreSSL

  - number of MKA/MACsec fixes and extensions

  - extended domain_match and domain_suffix_match to allow     list of values

  - fixed dNSName matching in domain_match and     domain_suffix_match when using wolfSSL

  - started to prefer FT-EAP-SHA384 over WPA-EAP-SUITE-B-192     AKM if both are enabled

  - extended nl80211 Connect and external authentication to     support SAE, FT-SAE, FT-EAP-SHA384

  - fixed KEK2 derivation for FILS+FT

  - extended client_cert file to allow loading of a chain of     PEM encoded certificates

  - extended beacon reporting functionality

  - extended D-Bus interface with number of new properties

  - fixed a regression in FT-over-DS with mac80211-based     drivers

  - OpenSSL: allow systemwide policies to be overridden

  - extended driver flags indication for separate 802.1X and     PSK 4-way handshake offload capability

  - added support for random P2P Device/Interface Address     use

  - extended PEAP to derive EMSK to enable use with ERP/FILS

  - extended WPS to allow SAE configuration to be added     automatically for PSK (wps_cred_add_sae=1)

  - removed support for the old D-Bus interface     (CONFIG_CTRL_IFACE_DBUS)

  - extended domain_match and domain_suffix_match to allow     list of values

  - added a RSN workaround for misbehaving PMF APs that     advertise IGTK/BIP KeyID using incorrect byte order

  - fixed PTK rekeying with FILS and FT

  - fixed WPA packet number reuse with replayed messages and     key reinstallation [https://w1.fi/security/2017-1/]     (CVE-2017-13077, CVE-2017-13078, CVE-2017-13079,     CVE-2017-13080, CVE-2017-13081, CVE-2017-13082,     CVE-2017-13086, CVE-2017-13087, CVE-2017-13088)

  - fixed unauthenticated EAPOL-Key decryption in     wpa_supplicant [https://w1.fi/security/2018-1/]     (CVE-2018-14526)

  - added support for FILS (IEEE 802.11ai) shared key     authentication

  - added support for OWE (Opportunistic Wireless     Encryption, RFC 8110; and transition mode defined by     WFA)

  - added support for DPP (Wi-Fi Device Provisioning     Protocol)

  - added support for RSA 3k key case with Suite B 192-bit     level

  - fixed Suite B PMKSA caching not to update PMKID during     each 4-way handshake

  - fixed EAP-pwd pre-processing with PasswordHashHash

  - added EAP-pwd client support for salted passwords

  - fixed a regression in TDLS prohibited bit validation

  - started to use estimated throughput to avoid undesired     signal strength based roaming decision

  - MACsec/MKA :

  - new macsec_linux driver interface support for the Linux     kernel macsec module

  - number of fixes and extensions

  - added support for external persistent storage of PMKSA     cache (PMKSA_GET/PMKSA_ADD control interface commands;
    and MESH_PMKSA_GET/MESH_PMKSA_SET for the mesh case)

  - fixed mesh channel configuration pri/sec switch case

  - added support for beacon report

  - large number of other fixes, cleanup, and extensions

  - added support for randomizing local address for GAS     queries (gas_rand_mac_addr parameter)

  - fixed EAP-SIM/AKA/AKA' ext auth cases within TLS tunnel

  - added option for using random WPS UUID (auto_uuid=1)

  - added SHA256-hash support for OCSP certificate matching

  - fixed EAP-AKA' to add AT_KDF into     Synchronization-Failure

  - fixed a regression in RSN pre-authentication candidate     selection

  - added option to configure allowed group management     cipher suites (group_mgmt network profile parameter)

  - removed all PeerKey functionality

  - fixed nl80211 AP and mesh mode configuration regression     with Linux 4.15 and newer

  - added ap_isolate configuration option for AP mode

  - added support for nl80211 to offload 4-way handshake     into the driver

  - added support for using wolfSSL cryptographic library

  - SAE

  - added support for configuring SAE password separately of     the WPA2 PSK/passphrase

  - fixed PTK and EAPOL-Key integrity and key-wrap algorithm     selection for SAE; note: this is not backwards     compatible, i.e., both the AP and station side     implementations will need to be update at the same time     to maintain interoperability

  - added support for Password Identifier

  - fixed FT-SAE PMKID matching

  - Hotspot 2.0

  - added support for fetching of Operator Icon Metadata     ANQP-element

  - added support for Roaming Consortium Selection element

  - added support for Terms and Conditions

  - added support for OSEN connection in a shared RSN BSS

  - added support for fetching Venue URL information

  - added support for using OpenSSL 1.1.1

  - FT

  - disabled PMKSA caching with FT since it is not fully     functional

  - added support for SHA384 based AKM

  - added support for BIP ciphers BIP-CMAC-256,     BIP-GMAC-128, BIP-GMAC-256 in addition to previously     supported BIP-CMAC-128

  - fixed additional IE inclusion in Reassociation Request     frame when using FT protocol

Limit P2P_DEVICE name to appropriate ifname size.

Enable SAE support(jsc#SLE-14992).

CVE-2019-16275: AP mode PMF disconnection protection bypass (bsc#1150934)

Fix wicked wlan (bsc#1156920)

Still include fi.epitest.hostap.WPASupplicant.service (bsc#1167331)

Change wpa_supplicant.service to ensure wpa_supplicant gets started before network. Fix WLAN config on boot with wicked. (bsc#1166933)

Adjust the service to start after network.target wrt bsc#1165266

Using O_WRONLY flag [http://w1.fi/security/2015-5/] (CVE-2015-8041)

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

This update for wpa_supplicant fixes the following issues :

Security issue fixed :

CVE-2019-16275: Fixed an AP mode PMF disconnection protection bypass (bsc#1150934).

Non-security issues fixed :

Enable SAE support (jsc#SLE-14992).

Limit P2P_DEVICE name to appropriate ifname size.

Fix wicked wlan (bsc#1156920)

Restore fi.epitest.hostap.WPASupplicant.service (bsc#1167331)

With v2.9 fi.epitest.hostap.WPASupplicant.service is obsolete (bsc#1167331)

Fix WLAN config on boot with wicked. (bsc#1166933)

Update to 2.9 release :

  - SAE changes

  - disable use of groups using Brainpool curves

  - improved protection against side channel attacks

[https://w1.fi/security/2019-6/]

  - EAP-pwd changes

  - disable use of groups using Brainpool curves

  - allow the set of groups to be configured     (eap_pwd_groups)

  - improved protection against side channel attacks

[https://w1.fi/security/2019-6/]

  - fixed FT-EAP initial mobility domain association using     PMKSA caching (disabled by default for backwards     compatibility; can be enabled with     ft_eap_pmksa_caching=1)

  - fixed a regression in OpenSSL 1.1+ engine loading

  - added validation of RSNE in (Re)Association Response     frames

  - fixed DPP bootstrapping URI parser of channel list

  - extended EAP-SIM/AKA fast re-authentication to allow use     with FILS

  - extended ca_cert_blob to support PEM format

  - improved robustness of P2P Action frame scheduling

  - added support for EAP-SIM/AKA using anonymous@realm     identity

  - fixed Hotspot 2.0 credential selection based on roaming     consortium to ignore credentials without a specific EAP     method

  - added experimental support for EAP-TEAP peer (RFC 7170)

  - added experimental support for EAP-TLS peer with TLS     v1.3

  - fixed a regression in WMM parameter configuration for a     TDLS peer

  - fixed a regression in operation with drivers that     offload 802.1X 4-way handshake

  - fixed an ECDH operation corner case with OpenSSL

  - SAE changes

  - added support for SAE Password Identifier

  - changed default configuration to enable only groups 19,     20, 21

(i.e., disable groups 25 and 26) and disable all unsuitable groups

completely based on REVmd changes

  - do not regenerate PWE unnecessarily when the AP uses the

anti-clogging token mechanisms

  - fixed some association cases where both SAE and FT-SAE     were enabled on both the station and the selected AP

  - started to prefer FT-SAE over SAE AKM if both are     enabled

  - started to prefer FT-SAE over FT-PSK if both are enabled

  - fixed FT-SAE when SAE PMKSA caching is used

  - reject use of unsuitable groups based on new     implementation

guidance in REVmd (allow only FFC groups with prime >= 3072 bits and ECC

groups with prime >= 256)

  - minimize timing and memory use differences in PWE     derivation

[https://w1.fi/security/2019-1/] (CVE-2019-9494, bsc#1131868)

  - EAP-pwd changes

  - minimize timing and memory use differences in PWE     derivation

[https://w1.fi/security/2019-2/] (CVE-2019-9495, bsc#1131870)

  - verify server scalar/element     [https://w1.fi/security/2019-4/]

(CVE-2019-9497, CVE-2019-9498, CVE-2019-9499, bsc#1131874, bsc#1131872,

bsc#1131871, bsc#1131644)

  - fix message reassembly issue with unexpected fragment

[https://w1.fi/security/2019-5/] (CVE-2019-11555, bsc#1133640)

  - enforce rand,mask generation rules more strictly

  - fix a memory leak in PWE derivation

  - disallow ECC groups with a prime under 256 bits (groups     25, 26, and

27)

  - SAE/EAP-pwd side-channel attack update

[https://w1.fi/security/2019-6/] (CVE-2019-13377, bsc#1144443)

  - fixed CONFIG_IEEE80211R=y (FT) build without     CONFIG_FILS=y

  - Hotspot 2.0 changes

  - do not indicate release number that is higher than the     one AP

supports

  - added support for release number 3

  - enable PMF automatically for network profiles created     from

credentials

  - fixed OWE network profile saving

  - fixed DPP network profile saving

  - added support for RSN operating channel validation     (CONFIG_OCV=y and network profile parameter ocv=1)

  - added Multi-AP backhaul STA support

  - fixed build with LibreSSL

  - number of MKA/MACsec fixes and extensions

  - extended domain_match and domain_suffix_match to allow     list of values

  - fixed dNSName matching in domain_match and     domain_suffix_match when using wolfSSL

  - started to prefer FT-EAP-SHA384 over WPA-EAP-SUITE-B-192     AKM if both are enabled

  - extended nl80211 Connect and external authentication to     support SAE, FT-SAE, FT-EAP-SHA384

  - fixed KEK2 derivation for FILS+FT

  - extended client_cert file to allow loading of a chain of     PEM encoded certificates

  - extended beacon reporting functionality

  - extended D-Bus interface with number of new properties

  - fixed a regression in FT-over-DS with mac80211-based     drivers

  - OpenSSL: allow systemwide policies to be overridden

  - extended driver flags indication for separate 802.1X and     PSK 4-way handshake offload capability

  - added support for random P2P Device/Interface Address     use

  - extended PEAP to derive EMSK to enable use with ERP/FILS

  - extended WPS to allow SAE configuration to be added     automatically for PSK (wps_cred_add_sae=1)

  - removed support for the old D-Bus interface     (CONFIG_CTRL_IFACE_DBUS)

  - extended domain_match and domain_suffix_match to allow     list of values

  - added a RSN workaround for misbehaving PMF APs that     advertise IGTK/BIP KeyID using incorrect byte order

  - fixed PTK rekeying with FILS and FT

  - fixed WPA packet number reuse with replayed messages and     key reinstallation [https://w1.fi/security/2017-1/]     (CVE-2017-13077, CVE-2017-13078, CVE-2017-13079,     CVE-2017-13080, CVE-2017-13081, CVE-2017-13082,     CVE-2017-13086, CVE-2017-13087, CVE-2017-13088)

  - fixed unauthenticated EAPOL-Key decryption in     wpa_supplicant [https://w1.fi/security/2018-1/]     (CVE-2018-14526)

  - added support for FILS (IEEE 802.11ai) shared key     authentication

  - added support for OWE (Opportunistic Wireless     Encryption, RFC 8110; and transition mode defined by     WFA)

  - added support for DPP (Wi-Fi Device Provisioning     Protocol)

  - added support for RSA 3k key case with Suite B 192-bit     level

  - fixed Suite B PMKSA caching not to update PMKID during     each 4-way handshake

  - fixed EAP-pwd pre-processing with PasswordHashHash

  - added EAP-pwd client support for salted passwords

  - fixed a regression in TDLS prohibited bit validation

  - started to use estimated throughput to avoid undesired     signal strength based roaming decision

  - MACsec/MKA :

  - new macsec_linux driver interface support for the Linux     kernel

macsec module

  - number of fixes and extensions

  - added support for external persistent storage of PMKSA     cache (PMKSA_GET/PMKSA_ADD control interface commands;
    and MESH_PMKSA_GET/MESH_PMKSA_SET for the mesh case)

  - fixed mesh channel configuration pri/sec switch case

  - added support for beacon report

  - large number of other fixes, cleanup, and extensions

  - added support for randomizing local address for GAS     queries (gas_rand_mac_addr parameter)

  - fixed EAP-SIM/AKA/AKA' ext auth cases within TLS tunnel

  - added option for using random WPS UUID (auto_uuid=1)

  - added SHA256-hash support for OCSP certificate matching

  - fixed EAP-AKA' to add AT_KDF into     Synchronization-Failure

  - fixed a regression in RSN pre-authentication candidate     selection

  - added option to configure allowed group management     cipher suites (group_mgmt network profile parameter)

  - removed all PeerKey functionality

  - fixed nl80211 AP and mesh mode configuration regression     with Linux 4.15 and newer

  - added ap_isolate configuration option for AP mode

  - added support for nl80211 to offload 4-way handshake     into the driver

  - added support for using wolfSSL cryptographic library

  - SAE

  - added support for configuring SAE password separately of     the WPA2

PSK/passphrase

  - fixed PTK and EAPOL-Key integrity and key-wrap algorithm     selection

for SAE; note: this is not backwards compatible, i.e., both the AP and

station side implementations will need to be update at the same time to

maintain interoperability

  - added support for Password Identifier

  - fixed FT-SAE PMKID matching

  - Hotspot 2.0

  - added support for fetching of Operator Icon Metadata     ANQP-element

  - added support for Roaming Consortium Selection element

  - added support for Terms and Conditions

  - added support for OSEN connection in a shared RSN BSS

  - added support for fetching Venue URL information

  - added support for using OpenSSL 1.1.1

  - FT

  - disabled PMKSA caching with FT since it is not fully     functional

  - added support for SHA384 based AKM

  - added support for BIP ciphers BIP-CMAC-256,     BIP-GMAC-128,

BIP-GMAC-256 in addition to previously supported BIP-CMAC-128

  - fixed additional IE inclusion in Reassociation Request     frame when

using FT protocol

Changed service-files for start after network (systemd-networkd).

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

This update for wpa_supplicant fixes the following issues :

Security issue fixed :

  - CVE-2019-16275: Fixed an AP mode PMF disconnection     protection bypass (bsc#1150934).

Non-security issues fixed :

  - Enable SAE support (jsc#SLE-14992).

  - Limit P2P_DEVICE name to appropriate ifname size.

  - Fix wicked wlan (bsc#1156920)

  - Restore fi.epitest.hostap.WPASupplicant.service     (bsc#1167331)

  - With v2.9 fi.epitest.hostap.WPASupplicant.service is     obsolete (bsc#1167331)

  - Fix WLAN config on boot with wicked. (bsc#1166933)

  - Update to 2.9 release :

  - SAE changes

  - disable use of groups using Brainpool curves

  - improved protection against side channel attacks     [https://w1.fi/security/2019-6/]

  - EAP-pwd changes

  - disable use of groups using Brainpool curves

  - allow the set of groups to be configured     (eap_pwd_groups)

  - improved protection against side channel attacks     [https://w1.fi/security/2019-6/]

  - fixed FT-EAP initial mobility domain association using     PMKSA caching (disabled by default for backwards     compatibility; can be enabled with     ft_eap_pmksa_caching=1)

  - fixed a regression in OpenSSL 1.1+ engine loading

  - added validation of RSNE in (Re)Association Response     frames

  - fixed DPP bootstrapping URI parser of channel list

  - extended EAP-SIM/AKA fast re-authentication to allow use     with FILS

  - extended ca_cert_blob to support PEM format

  - improved robustness of P2P Action frame scheduling

  - added support for EAP-SIM/AKA using anonymous@realm     identity

  - fixed Hotspot 2.0 credential selection based on roaming     consortium to ignore credentials without a specific EAP     method

  - added experimental support for EAP-TEAP peer (RFC 7170)

  - added experimental support for EAP-TLS peer with TLS     v1.3

  - fixed a regression in WMM parameter configuration for a     TDLS peer

  - fixed a regression in operation with drivers that     offload 802.1X 4-way handshake

  - fixed an ECDH operation corner case with OpenSSL

  - SAE changes

  - added support for SAE Password Identifier

  - changed default configuration to enable only groups 19,     20, 21 (i.e., disable groups 25 and 26) and disable all     unsuitable groups completely based on REVmd changes

  - do not regenerate PWE unnecessarily when the AP uses the     anti-clogging token mechanisms

  - fixed some association cases where both SAE and FT-SAE     were enabled on both the station and the selected AP

  - started to prefer FT-SAE over SAE AKM if both are     enabled

  - started to prefer FT-SAE over FT-PSK if both are enabled

  - fixed FT-SAE when SAE PMKSA caching is used

  - reject use of unsuitable groups based on new     implementation guidance in REVmd (allow only FFC groups     with prime >= 3072 bits and ECC groups with prime >=     256)

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-1/]     (CVE-2019-9494, bsc#1131868)

  - EAP-pwd changes

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-2/]     (CVE-2019-9495, bsc#1131870)

  - verify server scalar/element     [https://w1.fi/security/2019-4/] (CVE-2019-9497,     CVE-2019-9498, CVE-2019-9499, bsc#1131874, bsc#1131872,     bsc#1131871, bsc#1131644)

  - fix message reassembly issue with unexpected fragment     [https://w1.fi/security/2019-5/] (CVE-2019-11555,     bsc#1133640)

  - enforce rand,mask generation rules more strictly

  - fix a memory leak in PWE derivation

  - disallow ECC groups with a prime under 256 bits (groups     25, 26, and 27)

  - SAE/EAP-pwd side-channel attack update     [https://w1.fi/security/2019-6/] (CVE-2019-13377,     bsc#1144443)

  - fixed CONFIG_IEEE80211R=y (FT) build without     CONFIG_FILS=y

  - Hotspot 2.0 changes

  - do not indicate release number that is higher than the     one AP supports

  - added support for release number 3

  - enable PMF automatically for network profiles created     from credentials

  - fixed OWE network profile saving

  - fixed DPP network profile saving

  - added support for RSN operating channel validation     (CONFIG_OCV=y and network profile parameter ocv=1)

  - added Multi-AP backhaul STA support

  - fixed build with LibreSSL

  - number of MKA/MACsec fixes and extensions

  - extended domain_match and domain_suffix_match to allow     list of values

  - fixed dNSName matching in domain_match and     domain_suffix_match when using wolfSSL

  - started to prefer FT-EAP-SHA384 over WPA-EAP-SUITE-B-192     AKM if both are enabled

  - extended nl80211 Connect and external authentication to     support SAE, FT-SAE, FT-EAP-SHA384

  - fixed KEK2 derivation for FILS+FT

  - extended client_cert file to allow loading of a chain of     PEM encoded certificates

  - extended beacon reporting functionality

  - extended D-Bus interface with number of new properties

  - fixed a regression in FT-over-DS with mac80211-based     drivers

  - OpenSSL: allow systemwide policies to be overridden

  - extended driver flags indication for separate 802.1X and     PSK 4-way handshake offload capability

  - added support for random P2P Device/Interface Address     use

  - extended PEAP to derive EMSK to enable use with ERP/FILS

  - extended WPS to allow SAE configuration to be added     automatically for PSK (wps_cred_add_sae=1)

  - removed support for the old D-Bus interface     (CONFIG_CTRL_IFACE_DBUS)

  - extended domain_match and domain_suffix_match to allow     list of values

  - added a RSN workaround for misbehaving PMF APs that     advertise IGTK/BIP KeyID using incorrect byte order

  - fixed PTK rekeying with FILS and FT

  - fixed WPA packet number reuse with replayed messages and     key reinstallation [https://w1.fi/security/2017-1/]     (CVE-2017-13077, CVE-2017-13078, CVE-2017-13079,     CVE-2017-13080, CVE-2017-13081, CVE-2017-13082,     CVE-2017-13086, CVE-2017-13087, CVE-2017-13088)

  - fixed unauthenticated EAPOL-Key decryption in     wpa_supplicant [https://w1.fi/security/2018-1/]     (CVE-2018-14526)

  - added support for FILS (IEEE 802.11ai) shared key     authentication

  - added support for OWE (Opportunistic Wireless     Encryption, RFC 8110; and transition mode defined by     WFA)

  - added support for DPP (Wi-Fi Device Provisioning     Protocol)

  - added support for RSA 3k key case with Suite B 192-bit     level

  - fixed Suite B PMKSA caching not to update PMKID during     each 4-way handshake

  - fixed EAP-pwd pre-processing with PasswordHashHash

  - added EAP-pwd client support for salted passwords

  - fixed a regression in TDLS prohibited bit validation

  - started to use estimated throughput to avoid undesired     signal strength based roaming decision

  - MACsec/MKA :

  - new macsec_linux driver interface support for the Linux     kernel macsec module

  - number of fixes and extensions

  - added support for external persistent storage of PMKSA     cache (PMKSA_GET/PMKSA_ADD control interface commands;
    and MESH_PMKSA_GET/MESH_PMKSA_SET for the mesh case)

  - fixed mesh channel configuration pri/sec switch case

  - added support for beacon report

  - large number of other fixes, cleanup, and extensions

  - added support for randomizing local address for GAS     queries (gas_rand_mac_addr parameter)

  - fixed EAP-SIM/AKA/AKA' ext auth cases within TLS tunnel

  - added option for using random WPS UUID (auto_uuid=1)

  - added SHA256-hash support for OCSP certificate matching

  - fixed EAP-AKA' to add AT_KDF into     Synchronization-Failure

  - fixed a regression in RSN pre-authentication candidate     selection

  - added option to configure allowed group management     cipher suites (group_mgmt network profile parameter)

  - removed all PeerKey functionality

  - fixed nl80211 AP and mesh mode configuration regression     with Linux 4.15 and newer

  - added ap_isolate configuration option for AP mode

  - added support for nl80211 to offload 4-way handshake     into the driver

  - added support for using wolfSSL cryptographic library

  - SAE

  - added support for configuring SAE password separately of     the WPA2 PSK/passphrase

  - fixed PTK and EAPOL-Key integrity and key-wrap algorithm     selection for SAE; note: this is not backwards     compatible, i.e., both the AP and station side     implementations will need to be update at the same time     to maintain interoperability

  - added support for Password Identifier

  - fixed FT-SAE PMKID matching

  - Hotspot 2.0

  - added support for fetching of Operator Icon Metadata     ANQP-element

  - added support for Roaming Consortium Selection element

  - added support for Terms and Conditions

  - added support for OSEN connection in a shared RSN BSS

  - added support for fetching Venue URL information

  - added support for using OpenSSL 1.1.1

  - FT

  - disabled PMKSA caching with FT since it is not fully     functional

  - added support for SHA384 based AKM

  - added support for BIP ciphers BIP-CMAC-256,     BIP-GMAC-128, BIP-GMAC-256 in addition to previously     supported BIP-CMAC-128

  - fixed additional IE inclusion in Reassociation Request     frame when using FT protocol

  - Changed service-files for start after network     (systemd-networkd).

This update was imported from the SUSE:SLE-15:Update update project.

This update for hostapd fixes the following issues :

hostapd was updated to version 2.9 :

  - SAE changes

  - disable use of groups using Brainpool curves

  - improved protection against side channel attacks     [https://w1.fi/security/2019-6/]

  - EAP-pwd changes

  - disable use of groups using Brainpool curves

  - improved protection against side channel attacks     [https://w1.fi/security/2019-6/]

  - fixed FT-EAP initial mobility domain association using     PMKSA caching

  - added configuration of airtime policy

  - fixed FILS to and RSNE into (Re)Association Response     frames

  - fixed DPP bootstrapping URI parser of channel list

  - added support for regulatory WMM limitation (for ETSI)

  - added support for MACsec Key Agreement using IEEE     802.1X/PSK

  - added experimental support for EAP-TEAP server (RFC     7170)

  - added experimental support for EAP-TLS server with TLS     v1.3

  - added support for two server certificates/keys (RSA/ECC)

  - added AKMSuiteSelector into 'STA <addr>' control     interface data to determine with AKM was used for an     association

  - added eap_sim_id parameter to allow EAP-SIM/AKA server     pseudonym and fast reauthentication use to be disabled

  - fixed an ECDH operation corner case with OpenSSL

Update to version 2.8

  - SAE changes

  - added support for SAE Password Identifier

  - changed default configuration to enable only group 19     (i.e., disable groups 20, 21, 25, 26 from default     configuration) and disable all unsuitable groups     completely based on REVmd changes

  - improved anti-clogging token mechanism and SAE     authentication frame processing during heavy CPU load;
    this mitigates some issues with potential DoS attacks     trying to flood an AP with large number of SAE messages

  - added Finite Cyclic Group field in status code 77     responses

  - reject use of unsuitable groups based on new     implementation guidance in REVmd (allow only FFC groups     with prime >= 3072 bits and ECC groups with prime >=     256)

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-1/]     (CVE-2019-9494)

  - fixed confirm message validation in error cases     [https://w1.fi/security/2019-3/] (CVE-2019-9496)

  - EAP-pwd changes

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-2/]     (CVE-2019-9495)

  - verify peer scalar/element     [https://w1.fi/security/2019-4/] (CVE-2019-9497 and     CVE-2019-9498)

  - fix message reassembly issue with unexpected fragment     [https://w1.fi/security/2019-5/]

  - enforce rand,mask generation rules more strictly

  - fix a memory leak in PWE derivation

  - disallow ECC groups with a prime under 256 bits (groups     25, 26, and 27)

  - Hotspot 2.0 changes

  - added support for release number 3

  - reject release 2 or newer association without PMF

  - added support for RSN operating channel validation     (CONFIG_OCV=y and configuration parameter ocv=1)

  - added Multi-AP protocol support

  - added FTM responder configuration

  - fixed build with LibreSSL

  - added FT/RRB workaround for short Ethernet frame padding

  - fixed KEK2 derivation for FILS+FT

  - added RSSI-based association rejection from OCE

  - extended beacon reporting functionality

  - VLAN changes

  - allow local VLAN management with remote RADIUS     authentication

  - add WPA/WPA2 passphrase/PSK -based VLAN assignment

  - OpenSSL: allow systemwide policies to be overridden

  - extended PEAP to derive EMSK to enable use with ERP/FILS

  - extended WPS to allow SAE configuration to be added     automatically for PSK (wps_cred_add_sae=1)

  - fixed FT and SA Query Action frame with     AP-MLME-in-driver cases

  - OWE: allow Diffie-Hellman Parameter element to be     included with DPP in preparation for DPP protocol     extension

  - RADIUS server: started to accept ERP keyName-NAI as user     identity automatically without matching EAP database     entry

  - fixed PTK rekeying with FILS and FT

wpa_supplicant :

  - SAE changes

  - added support for SAE Password Identifier

  - changed default configuration to enable only groups 19,     20, 21 (i.e., disable groups 25 and 26) and disable all     unsuitable groups completely based on REVmd changes

  - do not regenerate PWE unnecessarily when the AP uses the     anti-clogging token mechanisms

  - fixed some association cases where both SAE and FT-SAE     were enabled on both the station and the selected AP

  - started to prefer FT-SAE over SAE AKM if both are     enabled

  - started to prefer FT-SAE over FT-PSK if both are enabled

  - fixed FT-SAE when SAE PMKSA caching is used

  - reject use of unsuitable groups based on new     implementation guidance in REVmd (allow only FFC groups     with prime >= 3072 bits and ECC groups with prime >=     256)

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-1/]     (CVE-2019-9494)

  - EAP-pwd changes

  - minimize timing and memory use differences in PWE     derivation [https://w1.fi/security/2019-2/]     (CVE-2019-9495)

  - verify server scalar/element     [https://w1.fi/security/2019-4/] (CVE-2019-9499)

  - fix message reassembly issue with unexpected fragment     [https://w1.fi/security/2019-5/]

  - enforce rand,mask generation rules more strictly

  - fix a memory leak in PWE derivation

  - disallow ECC groups with a prime under 256 bits (groups     25, 26, and 27)

  - fixed CONFIG_IEEE80211R=y (FT) build without     CONFIG_FILS=y

  - Hotspot 2.0 changes

  - do not indicate release number that is higher than the     one AP supports

  - added support for release number 3

  - enable PMF automatically for network profiles created     from credentials

  - fixed OWE network profile saving

  - fixed DPP network profile saving

  - added support for RSN operating channel validation     (CONFIG_OCV=y and network profile parameter ocv=1)

  - added Multi-AP backhaul STA support

  - fixed build with LibreSSL

  - number of MKA/MACsec fixes and extensions

  - extended domain_match and domain_suffix_match to allow     list of values

  - fixed dNSName matching in domain_match and     domain_suffix_match when using wolfSSL

  - started to prefer FT-EAP-SHA384 over WPA-EAP-SUITE-B-192     AKM if both are enabled

  - extended nl80211 Connect and external authentication to     support SAE, FT-SAE, FT-EAP-SHA384

  - fixed KEK2 derivation for FILS+FT

  - extended client_cert file to allow loading of a chain of     PEM encoded certificates

  - extended beacon reporting functionality

  - extended D-Bus interface with number of new properties

  - fixed a regression in FT-over-DS with mac80211-based     drivers

  - OpenSSL: allow systemwide policies to be overridden

  - extended driver flags indication for separate 802.1X and     PSK 4-way handshake offload capability

  - added support for random P2P Device/Interface Address     use

  - extended PEAP to derive EMSK to enable use with ERP/FILS

  - extended WPS to allow SAE configuration to be added     automatically for PSK (wps_cred_add_sae=1)

  - removed support for the old D-Bus interface     (CONFIG_CTRL_IFACE_DBUS)

  - extended domain_match and domain_suffix_match to allow     list of values

  - added a RSN workaround for misbehaving PMF APs that     advertise IGTK/BIP KeyID using incorrect byte order

  - fixed PTK rekeying with FILS and FT

  - Enabled CLI editing and history support.

Update to version 2.7

  - fixed WPA packet number reuse with replayed messages and     key reinstallation [http://w1.fi/security/2017-1/]     (CVE-2017-13082) (boo#1056061)

  - added support for FILS (IEEE 802.11ai) shared key     authentication

  - added support for OWE (Opportunistic Wireless     Encryption, RFC 8110; and transition mode defined by     WFA)

  - added support for DPP (Wi-Fi Device Provisioning     Protocol)

  - FT :

  - added local generation of PMK-R0/PMK-R1 for FT-PSK     (ft_psk_generate_local=1)

  - replaced inter-AP protocol with a cleaner design that is     more easily extensible; this breaks backward     compatibility and requires all APs in the ESS to be     updated at the same time to maintain FT functionality

  - added support for wildcard R0KH/R1KH

  - replaced r0_key_lifetime (minutes) parameter with     ft_r0_key_lifetime (seconds)

  - fixed wpa_psk_file use for FT-PSK

  - fixed FT-SAE PMKID matching

  - added expiration to PMK-R0 and PMK-R1 cache

  - added IEEE VLAN support (including tagged VLANs)

  - added support for SHA384 based AKM

  - SAE

  - fixed some PMKSA caching cases with SAE

  - added support for configuring SAE password separately of     the WPA2 PSK/passphrase

  - added option to require MFP for SAE associations     (sae_require_pmf=1)

  - fixed PTK and EAPOL-Key integrity and key-wrap algorithm     selection for SAE; note: this is not backwards     compatible, i.e., both the AP and station side     implementations will need to be update at the same time     to maintain interoperability

  - added support for Password Identifier

  - hostapd_cli: added support for command history and     completion

  - added support for requesting beacon report

  - large number of other fixes, cleanup, and extensions

  - added option to configure EAPOL-Key retry limits     (wpa_group_update_count and wpa_pairwise_update_count)

  - removed all PeerKey functionality

  - fixed nl80211 AP mode configuration regression with     Linux 4.15 and newer

  - added support for using wolfSSL cryptographic library

  - fixed some 20/40 MHz coexistence cases where the BSS     could drop to 20 MHz even when 40 MHz would be allowed

  - Hotspot 2.0

  - added support for setting Venue URL ANQP-element     (venue_url)

  - added support for advertising Hotspot 2.0 operator icons

  - added support for Roaming Consortium Selection element

  - added support for Terms and Conditions

  - added support for OSEN connection in a shared RSN BSS

  - added support for using OpenSSL 1.1.1

  - added EAP-pwd server support for salted passwords

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

  - hostapd before 2.10 and wpa_supplicant before 2.10     allow an incorrect indication of disconnection in     certain situations because source address validation is     mishandled. This is a denial of service that should     have been prevented by PMF (aka management frame     protection). The attacker must send a crafted 802.11     frame from a location that is within the 802.11     communications range.(CVE-2019-16275)

  - 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 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 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 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)

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.

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 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 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)

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.

Several vulnerabilities were discovered in WPA supplicant / hostapd.
Some of them could only partially be mitigated, please read below for details.

CVE-2019-9495

Cache-based side-channel attack against the EAP-pwd implementation: an attacker able to run unprivileged code on the target machine (including for example JavaScript code in a browser on a smartphone) during the handshake could deduce enough information to discover the password in a dictionary attack.

This issue has only very partially been mitigated against by reducing measurable timing differences during private key operations. More work is required to fully mitigate this vulnerability.

CVE-2019-9497

Reflection attack against EAP-pwd server implementation: a lack of validation of received scalar and elements value in the EAP-pwd-Commit messages could have resulted in attacks that would have been able to complete EAP-pwd authentication exchange without the attacker having to know the password. This did not result in the attacker being able to derive the session key, complete the following key exchange and access the network.

CVE-2019-9498

EAP-pwd server missing commit validation for scalar/element: hostapd didn't validate values received in the EAP-pwd-Commit message, so an attacker could have used a specially crafted commit message to manipulate the exchange in order for hostapd to derive a session key from a limited set of possible values. This could have resulted in an attacker being able to complete authentication and gain access to the network.

This issue could only partially be mitigated.

CVE-2019-9499

EAP-pwd peer missing commit validation for scalar/element:
wpa_supplicant didn't validate values received in the EAP-pwd-Commit message, so an attacker could have used a specially crafted commit message to manipulate the exchange in order for wpa_supplicant to derive a session key from a limited set of possible values. This could have resulted in an attacker being able to complete authentication and operate as a rogue AP.

This issue could only partially be mitigated.

CVE-2019-11555

The EAP-pwd implementation did't properly validate fragmentation reassembly state when receiving an unexpected fragment. This could have lead to a process crash due to a NULL pointer derefrence.

An attacker in radio range of a station or access point with EAP-pwd support could cause a crash of the relevant process (wpa_supplicant or hostapd), ensuring a denial of service.

For Debian 8 'Jessie', these problems have been fixed in version 2.3-1+deb8u8.

We recommend that you upgrade your wpa packages.

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

Update to version 2.7 from upstream Security fix for CVE-2019-9494 (cache attack against SAE) Security fix for CVE-2019-9495 (cache attack against EAP-pwd) Security fix for CVE-2019-9496 (SAE confirm missing state validation in hostapd/AP) Security fix for CVE-2019-9497 (EAP-pwd server not checking for reflection attack) Security fix for CVE-2019-9498 (EAP-pwd server missing commit validation for scalar/element) Security fix for CVE-2019-9499 (EAP-pwd peer missing commit validation for scalar/element)

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

include fix for :

CVE-2019-9494 CVE-2019-9495 CVE-2019-9496 CVE-2019-9497 CVE-2019-9498

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

EAP-pwd implementation in hostapd (EAP server) and wpa_supplicant (EAP peer) does not to validate the received scalar and element values in EAP-pwd-Commit messages properly. This could result in attacks that would be able to complete EAP-pwd authentication exchange without the attacker having to know the used password.

See https://w1.fi/security/2019-4/eap-pwd-missing-commit-validation.txt for a detailed description of the bug. Impact : All wpa_supplicant and hostapd versions with EAP-pwd support.

Mathy Vanhoef (NYUAD) and Eyal Ronen (Tel Aviv University & KU Leuven) found multiple vulnerabilities in the WPA implementation found in wpa_supplication (station) and hostapd (access point). These vulnerability are also collectively known as 'Dragonblood'.

  - CVE-2019-9495     Cache-based side-channel attack against the EAP-pwd     implementation: an attacker able to run unprivileged     code on the target machine (including for example     JavaScript code in a browser on a smartphone) during the     handshake could deduce enough information to discover     the password in a dictionary attack.

  - CVE-2019-9497     Reflection attack against EAP-pwd server implementation:
    a lack of validation of received scalar and elements     value in the EAP-pwd-Commit messages could result in     attacks that would be able to complete EAP-pwd     authentication exchange without the attacker having to     know the password. This does not result in the attacker     being able to derive the session key, complete the     following key exchange and access the network.

  - CVE-2019-9498     EAP-pwd server missing commit validation for     scalar/element: hostapd doesn't validate values received     in the EAP-pwd-Commit message, so an attacker could use     a specially crafted commit message to manipulate the     exchange in order for hostapd to derive a session key     from a limited set of possible values. This could result     in an attacker being able to complete authentication and     gain access to the network.

  - CVE-2019-9499     EAP-pwd peer missing commit validation for     scalar/element: wpa_supplicant doesn't validate values     received in the EAP-pwd-Commit message, so an attacker     could use a specially crafted commit message to     manipulate the exchange in order for wpa_supplicant to     derive a session key from a limited set of possible     values. This could result in an attacker being able to     complete authentication and operate as a rogue AP.

Note that the Dragonblood moniker also applies to CVE-2019-9494 and CVE-2014-9496 which are vulnerabilities in the SAE protocol in WPA3.
SAE is not enabled in Debian stretch builds of wpa, which is thus not vulnerable by default.

Due to the complexity of the backporting process, the fix for these vulnerabilities are partial. Users are advised to use strong passwords to prevent dictionary attacks or use a 2.7-based version from stretch-backports (version above 2:2.7+git20190128+0c1e29f-4).

The remote Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-3944-1 advisory.

    It was discovered that wpa_supplicant and hostapd were vulnerable to a side channel attack against EAP-     pwd. A remote attacker could possibly use this issue to recover certain passwords. (CVE-2019-9495)

    Mathy Vanhoef discovered that wpa_supplicant and hostapd incorrectly validated received scalar and element     values in EAP-pwd-Commit messages. A remote attacker could possibly use this issue to perform a reflection     attack and authenticate without the appropriate password. (CVE-2019-9497, CVE-2019-9498, CVE-2019-9499)

    It was discovered that hostapd incorrectly handled obtaining random numbers. In rare cases where the     urandom device isn't available, it would fall back to using a low-quality PRNG. This issue only affected     Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-10743)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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	Severity
202820	Photon OS 3.0: Wpa_Supplicant PHSA-2019-3.0-0011	Nessus	PhotonOS Local Security Checks	high
161651	SUSE SLES12 Security Update : wpa_supplicant (SUSE-SU-2022:1853-1)	Nessus	SuSE Local Security Checks	critical
143704	SUSE SLES12 Security Update : wpa_supplicant (SUSE-SU-2020:3424-1) (KRACK)	Nessus	SuSE Local Security Checks	high
143627	SUSE SLED15 / SLES15 Security Update : wpa_supplicant (SUSE-SU-2020:3380-1) (KRACK)	Nessus	SuSE Local Security Checks	high
143321	openSUSE Security Update : wpa_supplicant (openSUSE-2020-2053) (KRACK)	Nessus	SuSE Local Security Checks	high
143304	openSUSE Security Update : wpa_supplicant (openSUSE-2020-2059) (KRACK)	Nessus	SuSE Local Security Checks	high
133758	openSUSE Security Update : hostapd (openSUSE-2020-222) (KRACK)	Nessus	SuSE Local Security Checks	high
132827	EulerOS Virtualization for ARM 64 3.0.5.0 : wpa_supplicant (EulerOS-SA-2020-1073)	Nessus	Huawei Local Security Checks	high
132629	EulerOS 2.0 SP8 : wpa_supplicant (EulerOS-SA-2020-1036)	Nessus	Huawei Local Security Checks	high
127476	Debian DLA-1867-1 : wpa security update	Nessus	Debian Local Security Checks	high
124554	Fedora 30 : hostapd (2019-eba1109acd)	Nessus	Fedora Local Security Checks	high
124539	Fedora 30 : 1:wpa_supplicant (2019-ca49dfd42f)	Nessus	Fedora Local Security Checks	high
124252	Fedora 29 : hostapd (2019-f409af9fbe)	Nessus	Fedora Local Security Checks	high
124250	Fedora 28 : hostapd (2019-d03bae77f5)	Nessus	Fedora Local Security Checks	high
124219	FreeBSD : FreeBSD -- EAP-pwd missing commit validation (2da3cb25-6571-11e9-8e67-206a8a720317)	Nessus	FreeBSD Local Security Checks	high
124038	Debian DSA-4430-1 : wpa - security update	Nessus	Debian Local Security Checks	high
123999	Ubuntu 14.04 LTS / 16.04 LTS / 18.04 LTS : wpa_supplicant and hostapd vulnerabilities (USN-3944-1)	Nessus	Ubuntu Local Security Checks	high

Detections

Analytics

CVE-2019-9498

high

Tenable Plugins

high

critical

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high