CVE-2014-2015: Buffer Overflow

Published Feb 19, 2014
·
Updated

Pierre Carrier reported a stack-based buffer overflow flaw in the FreeRADIUS rlmpap module. An authenticated user could trigger this issue by creating a large password, causing FreeRADIUS to crash. The stack protector and SSP variable re-ordering protections should help prevent this issue from being used to execute arbitrary code.

Upstream fixes: 2.x: https://github.com/FreeRADIUS/freeradius-server/commit/0d606cfc29a 3.x: https://github.com/FreeRADIUS/freeradius-server/commit/ff5147c9e5088c7 master: https://github.com/FreeRADIUS/freeradius-server/commit/f610864d4c8f51d

References: http://lists.freebsd.org/pipermail/freebsd-bugbusters/2014-February/000610.html

Other sources

Stack-based buffer overflow in the normify function in the rlmpap module (modules/rlmpap/rlmpap.c) in FreeRADIUS 2.x, possibly 2.2.3 and earlier, and 3.x, possibly 3.0.1 and earlier, might allow attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long password hash, as demonstrated by an SSHA hash.

MITRE

Affected Software

24 affected components
FreeRADIUS freeradius=2.0
FreeRADIUS freeradius=2.0.1
FreeRADIUS freeradius=2.0.2
FreeRADIUS freeradius=2.0.3
FreeRADIUS freeradius=2.0.4
FreeRADIUS freeradius=2.0.5
FreeRADIUS freeradius=2.1.0
FreeRADIUS freeradius=2.1.1
FreeRADIUS freeradius=2.1.2
FreeRADIUS freeradius=2.1.3
FreeRADIUS freeradius=2.1.4
FreeRADIUS freeradius=2.1.6
FreeRADIUS freeradius=2.1.7
FreeRADIUS freeradius=2.1.8
FreeRADIUS freeradius=2.1.9
FreeRADIUS freeradius=2.1.10
FreeRADIUS freeradius=2.1.11
FreeRADIUS freeradius=2.1.12
FreeRADIUS freeradius=2.2.0
FreeRADIUS freeradius=2.2.1
FreeRADIUS freeradius=2.2.2
FreeRADIUS freeradius=2.2.3
FreeRADIUS freeradius=3.0.0
FreeRADIUS freeradius=3.0.1

Event History

Feb 19, 2014
Data Sourced
via Red Hat·04:46 AM
DescriptionSeverityAffected Software
Nov 2, 2014
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2014-2015?

CVE-2014-2015 is classified as a medium severity vulnerability due to its potential impact on service availability.

2

How do I fix CVE-2014-2015?

To mitigate CVE-2014-2015, users should upgrade FreeRADIUS to a patched version above 2.0.5 or apply appropriate workarounds to limit password size.

3

Who is affected by CVE-2014-2015?

CVE-2014-2015 affects FreeRADIUS versions from 2.0 to 3.0.1 that use the rlm_pap module.

4

What kind of attack can exploit CVE-2014-2015?

CVE-2014-2015 can be exploited by an authenticated user who deliberately provides an oversized password to crash the FreeRADIUS server.

5

Is CVE-2014-2015 already exploited in the wild?

As of the last update, there have been no confirmed public exploits targeting CVE-2014-2015 in the wild.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203