Skip to content
Fencer Intel
medium 5.9

CVE-2015-5316 json

The eap_pwd_perform_confirm_exchange function in eap_peer/eap_pwd.c in wpa_supplicant 2.x before 2.6, when EAP-pwd is enabled in a network…

published 8y ago modified 4mo ago also EUVD-2015-5287

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

Summary

The eap_pwd_perform_confirm_exchange function in eap_peer/eap_pwd.c in wpa_supplicant 2.x before 2.6, when EAP-pwd is enabled in a network configuration profile, allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an EAP-pwd Confirm message followed by the Identity exchange.

Patch / fix

  • w1.fi wpa_supplicant 2.6
  • wpa Debian 14, Debian 13, Debian 12 2.3-2.3

debian advisories DEBIAN-CVE-2015-5316

  • wpa_supplicant openSUSE Tumbleweed 2.6-1.1

opensuse advisories openSUSE-SU-2024:10499-1

Is CVE-2015-5316 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-5316 updated cvss 2.9

wpa_supplicant: EAP-pwd peer error path failure on unexpected Confirm message

  • 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.19% 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 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

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.