Red Hat Bugzilla – Bug 167676
CVE-2005-4744 Multiple freeradius security issues
Last modified: 2007-11-30 17:07:20 EST
A number of issues have been found in freeradius:
Off by one error (\0 being written to end of string, probably not even a crash)
Use per-system max fd to close, rather than hard-coded number
If strftime(3) returns 0, the contents of the string array is undefined,
therefore it should not be copied. This could lead to the leaking of 40 bytes
off the stack (random unitialized memory).
Adds boundly length checks, whithout which it could be possible to overflow a
var on the stack.
* As best as I can tell, this is coming from the server, not a malicious source.
Adds a boundry length check. Possible stack buffer overflow. This sould be a
Properly escape ldap data. This could possible leak ldap data via a malformed
query, without proper acls.
Make things a bit more thread safe by introducing a horrible horrible hack.
These issues may also affect RHEL3.
These issues should be considered public
After reading upstream's response to these issues, I'm marking the severity as
low. Given I'm not an expert with the FreeRADIUS source, I purposely marked
some of these issues as "moderate" severity to prevent us from not giving enough
attention to something that may have needed it.
After a short discussion with MITRE and some analysis, only the off my one error
in sql_unixodbc.c is being considered a security issue.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.