5.9
CVSSv3

CVE-2019-11555

Published: 26/04/2019 Updated: 07/11/2023
CVSS v2 Base Score: 4.3 | Impact Score: 2.9 | Exploitability Score: 8.6
CVSS v3 Base Score: 5.9 | Impact Score: 3.6 | Exploitability Score: 2.2
VMScore: 383
Vector: AV:N/AC:M/Au:N/C:N/I:N/A:P

Vulnerability Summary

The EAP-pwd implementation in hostapd (EAP server) prior to 2.8 and wpa_supplicant (EAP peer) prior to 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.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

w1.fi hostapd

w1.fi wpa supplicant

Vendor Advisories

Debian Bug report logs - #927463 wpa: CVE-2019-11555: EAP-pwd message reassembly issue with unexpected fragment Package: src:wpa; Maintainer for src:wpa is Debian wpasupplicant Maintainers <wpa@packagesdebianorg>; Reported by: Salvatore Bonaccorso <carnil@debianorg> Date: Sat, 20 Apr 2019 06:15:05 UTC Severity: im ...
wpa_supplicant and hostapd could be made to crash if they received specially crafted network traffic ...
wpa_supplicant and hostapd could be made to crash if they received specially crafted network traffic ...
A vulnerability was found in the WPA protocol implementation found in wpa_supplication (station) and hostapd (access point) The EAP-pwd implementation in hostapd (EAP server) and wpa_supplicant (EAP peer) doesn't properly validate fragmentation reassembly state when receiving an unexpected fragment This could lead to a process crash due to a NULL ...
Impact: Moderate Public Date: 2019-04-18 CWE: CWE-476 Bugzilla: 1703417: wpa_supplicant: Improper fragm ...

Mailing Lists

<!--X-Body-Begin--> <!--X-User-Header--> oss-sec mailing list archives <!--X-User-Header-End--> <!--X-TopPNI--> By Date By Thread </form> <!--X-TopPNI-End--> <!--X-MsgBody--> <!--X-Subject-Header-Begin--> Re: wpa_supplicant/hostapd: EAP-pwd message reassembly issue with unexpected fragment <!--X-Subject-Header-End--> <!--X-Head-o ...