Skip to content
Fencer Intel
medium 5.0

CVE-2015-4145 json

The EAP-pwd server and peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not validate a fragment is already being proc…

published 2015-06-15 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-4169

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.4%
EPSS 3.4% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

The EAP-pwd server and peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not validate a fragment is already being processed, which allows remote attackers to cause a denial of service (memory leak) via a crafted message.

Patch / fix

  • wpa Debian 14, Debian 13, Debian 12 2.3-2.2

debian advisories DEBIAN-CVE-2015-4145

  • wpa Ubuntu 14.04 LTS 2.1-0ubuntu1.3

ubuntu advisories UBUNTU-CVE-2015-4145

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • hostapd openSUSE Tumbleweed 2.6-1.1
  • wpa_supplicant openSUSE Tumbleweed 2.6-1.1

opensuse advisories openSUSE-SU-2024:10022-1openSUSE-SU-2024:10499-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-4145 updated cvss 2.9

hostapd: EAP-pwd missing payload length validation

  • Red Hat Enterprise Linux 5 wpa_supplicant Red Hat Enterprise Linux 6 wpa_supplicant Red Hat Enterprise Linux 7 wpa_supplicant
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.41% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-399 Resource Management Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.