Security Advisory

CVE-2019-11555: EAP-pwd Fragment Reassembly Crash

Last updated:
  • CVE-2019-11555

CVE-2019-11555 is a NULL pointer dereference (CWE-476) in the EAP-pwd fragment reassembly code of hostapd and wpa_supplicant before 2.8: an unexpected fragment ends the process. An attacker in radio range needs no credentials, only an EAP-pwd setup. NVD scores it 5.9; version 2.8 fixes it.

Vulnerability summary

CVSS base score

5.9

Medium severity

EPSS score (FIRST)

3.3%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-11555 · Source: NVD

Affected components

ComponentCPEVersion range
hostapd (EAP-pwd server)cpe:2.3:a:w1.fi:hostapd:*:*:*:*:*:*:*:*before 2.8 (NVD), with CONFIG_EAP_PWD=y and an EAP-pwd user configured
wpa_supplicant (EAP-pwd peer)cpe:2.3:a:w1.fi:wpa_supplicant:*:*:*:*:*:*:*:*before 2.8 (NVD), with CONFIG_EAP_PWD=y and an EAP-pwd network profile
OpenWrt wpad full variants—OpenWrt builds hostapd and wpa_supplicant from git snapshots dated 2026-08-07 on main, 2025-08-26 on openwrt-25.12 and 2024-09-15 on openwrt-24.10 (read 2026-11-18); full variants build CONFIG_EAP_PWD=y

What does this mean for affected devices?

NVD's description: "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)." It names eap_server/eap_server_pwd.c and eap_peer/eap_pwd.c. NVD's Primary score is CVSS v3.0 5.9 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) and CVSS v2 4.3, with CWE-476. The record was published on 2019-04-26 (NVD).

Who can trigger it?

The w1.fi 2019-5 advisory, published 2019-04-18, describes both sides. "An attacker in radio range of a station device with wpa_supplicant network profile enabling use of EAP-pwd could cause the wpa_supplicant process to terminate by constructing unexpected sequence of EAP messages." On the network side, the same applies to an access point "that points to hostapd as an authentication server with EAP-pwd user enabled in runtime configuration", and to non-WLAN uses of EAP "as long as the attacker can send EAP-pwd messages to the server." The affected configurations are all versions with CONFIG_EAP_PWD=y and EAP-pwd enabled at runtime. It is a crash, not a key leak; the EAP-pwd side-channel and reflection flaws of the same month are CVE-2019-9495 and CVE-2019-9497.

Which builds carry EAP-pwd?

EAP-pwd is a build option. OpenWrt's hostapd Makefile adds CONFIG_EAP_PWD=y only to its full variants for OpenSSL, wolfSSL and mbed TLS (such as wpad-openssl), not to the basic, mesh or mini variants. Buildroot's hostapd and wpa_supplicant recipes, at 2.12, disable CONFIG_EAP_PWD unless OpenSSL is selected. The Debian security tracker lists fixed wpa packages 2.3-1+deb8u8 for jessie and 2:2.4-1+deb9u4 for stretch (DSA-4450-1). We found no device vendor advisory that names this CVE; our hostapd and wpa_supplicant firmware guide explains how to find CONFIG_EAP_PWD in a binary.

How do you fix or mitigate it?

Ship hostapd and wpa_supplicant 2.8 or later, or merge the two w1.fi commits "EAP-pwd peer: Fix reassembly buffer handling" and "EAP-pwd server: Fix reassembly buffer handling". If EAP-pwd is not used, build without CONFIG_EAP_PWD or remove EAP-pwd from the user and network profiles. The memory corruption fix guide covers state checks before pointer use. Related hostapd pages: CVE-2019-13377 and CVE-2015-4141.

CVE-2019-11555 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.03252, the 88.6th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • NVD: EAP-pwd in hostapd (server) and wpa_supplicant (peer) before 2.8 does not validate fragmentation reassembly state for an unexpected fragment; NULL pointer dereference DoS; eap_server_pwd.c and eap_pwd.c; Primary CVSS v3.0 5.9 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, CVSS v2 4.3; CWE-476; published 2019-04-26. — NVD
  • w1.fi 2019-5 (2019-04-18): attacker in radio range of a station with an EAP-pwd profile, or of an AP using hostapd as authentication server with an EAP-pwd user, can terminate the process; all versions with CONFIG_EAP_PWD=y and EAP-pwd enabled; fix commits listed; update to v2.8. — w1.fi
  • OpenWrt hostapd Makefile: CONFIG_EAP_PWD=y only in the full variant for OpenSSL, wolfSSL and mbed TLS; PKG_SOURCE_DATE 2026-08-07 on main. — OpenWrt
  • Buildroot hostapd.mk 2.12: CONFIG_EAP_PWD disabled when libopenssl is not selected. — Buildroot
  • Buildroot wpa_supplicant.mk 2.12: CONFIG_EAP_PWD disabled when libopenssl is not selected. — Buildroot
  • Debian: wpa fixed 2.3-1+deb8u8 (jessie, DLA-1867-1), 2:2.4-1+deb9u4 (stretch, DSA-4450-1). — Debian security tracker
  • CVE-2019-11555 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.03252, percentile 0.88560, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. w1.fi security advisory 2019-5
  3. OpenWrt: hostapd package Makefile
  4. Buildroot: hostapd recipe
  5. Buildroot: wpa_supplicant recipe
  6. Debian security tracker
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Which hostapd and wpa_supplicant versions are affected by CVE-2019-11555?

NVD lists both before 2.8. w1.fi says all versions with EAP-pwd support are vulnerable, meaning CONFIG_EAP_PWD=y in the build and EAP-pwd enabled at runtime (per NVD and w1.fi advisory 2019-5).

Does an attacker need credentials for CVE-2019-11555?

No. An attacker in radio range can send an unexpected sequence of EAP-pwd messages to a station with an EAP-pwd profile, or to an access point whose hostapd authentication server has an EAP-pwd user, and make the process exit (per w1.fi advisory 2019-5).

Is CVE-2019-11555 in a typical OpenWrt router image?

Only with a full variant. OpenWrt enables CONFIG_EAP_PWD in its full OpenSSL, wolfSSL and mbed TLS variants such as wpad-openssl, not in the basic, mesh or mini variants, and it builds from hostapd snapshots dated 2024 to 2026 (per the OpenWrt hostapd Makefile).

Is CVE-2019-11555 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.03252, the 88.6th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).