Fedora Commons LDAP server security bypass
| fedora-ldap-security-bypass (36005) |  Medium Risk |
Description:
Fedora Commons could allow a remote attacker to bypass security restrictions, caused by an error while binding to the LDAP server using an empty password. Certain LDAP implementations return a success code, which would allow an attacker to exploit this vulnerability to bypass authentication and gain unauthorized access to the affected application.
Platforms Affected:
- Fedora Commons, Fedora Commons prior to 2.2.1
Remedy:
Upgrade to the latest version of Fedora Commons (2.2.1 or later), available from SourceForge.net : Files. See References.
Consequences:
Bypass Security
References:
- SourceForge.net : Files, Fedora Commons - File Release Notes and Changelog - Release Name: 2.2.1 at http://sourceforge.net/project/shownotes.php?release_id=531870.
- BID-25317: Fedora Commons LDAP Authentication Bypass Vulnerability
- CVE-2007-4364: Fedora Commons before 2.2.1 does not properly handle certain authentication requests involving Java Naming and Directory Interface (JNDI), related to (1) a nonexistent account name in combination with an empty password, which allows remote attackers to trigger a certain unexpected / strange response from an LDAP server, and (2) a reauthentication attempt that throws an exception, which allows remote attackers to trigger use of a cached authentication decision. NOTE: authentication can be bypassed by using vector 1 followed by vector 2, and possibly can be bypassed by using a single vector.
- SA26445: Fedora Commons Empty LDAP Passwords Authentication Bypass
Reported:
Aug 13, 2007
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net