Skip to content
Fencer Intel
high 8.1

CVE-2015-8763 json

The EAP-PWD module in FreeRADIUS 3.0 through 3.0.8 allows remote attackers to have unspecified impact via a crafted (1) commit or (2) confi…

published 2017-03-27 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8636

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

Summary

The EAP-PWD module in FreeRADIUS 3.0 through 3.0.8 allows remote attackers to have unspecified impact via a crafted (1) commit or (2) confirm message, which triggers an out-of-bounds read.

Patch / fix

  • freeradius-server openSUSE Tumbleweed 3.0.23-1.5

opensuse advisories openSUSE-SU-2024:10767-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-8763 updated cvss 2.9

freeradius: the EAP-PWD module performs insufficient validation on packets received from an EAP peer

  • Red Hat Enterprise Linux 7 freeradius, freeradius-krb5, freeradius-ldap, freeradius-perl, freeradius-mysql, freeradius-utils, +4 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 freeradius Red Hat Enterprise Linux 6 freeradius, freeradius-krb5, freeradius-ldap, freeradius-perl, freeradius-mysql, freeradius-utils, +3 more
    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

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

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/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.