CVE-2010-3697: Medium severity FreeRADIUS freeradius vulnerability
It was reported [1],[2] that an error when processing requests queued for more than 30 seconds in src/main/event.c could be exploited to cause the process to crash by sending a large number of requests for an extended period of time.
This flaw seems to only affect 2.1.x and was fixed [3] in 2.1.10.
[1] https://bugs.freeradius.org/bugzilla/showbug.cgi?id=35 [2] http://secunia.com/advisories/41621 [3] http://github.com/alandekok/freeradius-server/commit/ff94dd35673bba1476594299d31ce8293b8bd223
The offending file (event.c), nor the affected function (waitforchildtodie()) are not present in the version of freeradius as provided with Red Hat Enterprise Linux 5 (1.1.3).
Other sources
The waitforchildtodie function in main/event.c in FreeRADIUS 2.1.x before 2.1.10, in certain circumstances involving long-term database outages, does not properly handle long queue times for requests, which allows remote attackers to cause a denial of service (daemon crash) by sending many requests.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3697?
CVE-2010-3697 has been classified as medium severity due to its potential for denial-of-service attacks.
How do I fix CVE-2010-3697?
To fix CVE-2010-3697, upgrade FreeRADIUS to version 2.1.10 or later, where the vulnerability has been addressed.
Which versions of FreeRADIUS are affected by CVE-2010-3697?
CVE-2010-3697 affects FreeRADIUS versions 2.1.0 through 2.1.9.
What type of attack does CVE-2010-3697 enable?
CVE-2010-3697 enables a denial-of-service attack by allowing an attacker to crash the process through excessive requests.
Is CVE-2010-3697 specific to certain operating systems?
CVE-2010-3697 is not specific to operating systems; it affects any system running the vulnerable versions of FreeRADIUS.