OpenLDAP CRYPT password gain access
|openldap-crypt-gain-access (17300)||Medium Risk|
OpenLDAP stores the CRYPT password in the userPassword attribute. This value may be used as a plaintext password by certain authentication validation schemes. A remote attacker, with knowledge of the CRYPT password, could login as the victim and gain unauthorized access.
For Mac OS X:
Apply the fix for this vulnerability, as listed in Apple Security Update 2004-09-07. See References.
For Red Hat Linux:
Refer to RHSA-2005:751-23 for patch, upgrade, or suggested workaround information. See References.
- CIAC Information Bulletin O-212: Apple Security Update.
- ASA-2006-157: openldap and nss_ldap security update
- BID-11137: OpenLDAP Ambiguous Password Attribute Weakness
- CVE-2004-0823: OpenLDAP 1.0 through 2.1.19, as used in Apple Mac OS 10.3.4 and 10.3.5 and possibly other operating systems, may allow certain authentication schemes to use hashed (crypt) passwords in the userPassword attribute as if they were plaintext passwords, which allows remote attackers to re-use hashed passwords without decrypting them.
- RHSA-2005-751: openldap and nss_ldap security update
- SA12491: Mac OS X Security Update Fixes Multiple Vulnerabilities
- SA21520: Avaya Products Multiple Vulnerabilities
- Apple Mac OS X 10.3.4
- Apple Mac OS X 10.3.5
- Apple Mac OS X Server 10.3.4
- Apple Mac OS X Server 10.3.5
- OpenLDAP OpenLDAP
- RedHat Enterprise Linux 2.1 WS
- RedHat Enterprise Linux 2.1 AS
- RedHat Enterprise Linux 2.1 ES
- RedHat Enterprise Linux 3 Desktop
- RedHat Enterprise Linux 3 ES
- RedHat Enterprise Linux 3 WS
- RedHat Enterprise Linux 3 AS
- RedHat Linux Advanced Workstation 2.1 Itanium
Sep 07, 2004
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 ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this