Skip to content
OpenAdvisories
Unscored SUSE-SU-2020:3424-1 19 CVEs

Security update for wpa_supplicant

Published Nov 19, 2020 · Updated Feb 4, 2026

Summary

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 S

Fixed packages 2

ReleasePackageFixed in
SUSE · SLES 12 SP5 Linux Enterprise Server 12 SP5 wpa_supplicant 2.9-23.3.1
SUSE · SLES for SAP 12 SP5 Linux Enterprise Server for SAP Applications 12 SP5 wpa_supplicant 2.9-23.3.1

Vulnerabilities 19

References

  • report
    https://bugzilla.suse.com/1131644
  • report
    https://bugzilla.suse.com/1131868
  • report
    https://bugzilla.suse.com/1131870
  • report
    https://bugzilla.suse.com/1131871
  • report
    https://bugzilla.suse.com/1131872
  • report
    https://bugzilla.suse.com/1131874
  • report
    https://bugzilla.suse.com/1133640
  • report
    https://bugzilla.suse.com/1144443
  • report
    https://bugzilla.suse.com/1150934
  • report
    https://bugzilla.suse.com/1156920
  • report
    https://bugzilla.suse.com/1165266
  • report
    https://bugzilla.suse.com/1166933
  • report
    https://bugzilla.suse.com/1167331
  • web
    https://www.suse.com/security/cve/CVE-2015-8041
  • web
    https://www.suse.com/security/cve/CVE-2017-13077
  • web
    https://www.suse.com/security/cve/CVE-2017-13078
  • web
    https://www.suse.com/security/cve/CVE-2017-13079
  • web
    https://www.suse.com/security/cve/CVE-2017-13080
  • web
    https://www.suse.com/security/cve/CVE-2017-13081
  • web
    https://www.suse.com/security/cve/CVE-2017-13082
  • web
    https://www.suse.com/security/cve/CVE-2017-13086
  • web
    https://www.suse.com/security/cve/CVE-2017-13087
  • web
    https://www.suse.com/security/cve/CVE-2017-13088
  • web
    https://www.suse.com/security/cve/CVE-2018-14526
  • web
    https://www.suse.com/security/cve/CVE-2019-11555
  • web
    https://www.suse.com/security/cve/CVE-2019-13377
  • web
    https://www.suse.com/security/cve/CVE-2019-16275
  • web
    https://www.suse.com/security/cve/CVE-2019-9494
  • web
    https://www.suse.com/security/cve/CVE-2019-9495
  • web
    https://www.suse.com/security/cve/CVE-2019-9497
  • web
    https://www.suse.com/security/cve/CVE-2019-9498
  • web
    https://www.suse.com/security/cve/CVE-2019-9499