|Summary:||CAN-2005-2069 openldap password disclosure issue|
|Product:||[Fedora] Fedora||Reporter:||Josh Bressers <bressers>|
|Component:||nss_ldap||Assignee:||Nalin Dahyabhai <nalin>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-02-17 21:08:06 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Josh Bressers 2005-07-05 14:20:00 UTC
+++ This bug was initially created as a clone of Bug #162482 +++ This information is from Rob Holland Openldap currently doesn't allow a client to specify that referred connections should use TLS. This can lead to passwords being sent in the clear despite having "ssl start_tls" in ldap.conf. In a master+slaves LDAP infrastructure passwords are sent in the clear when a user runs "passwd" on a machine where pam_ldap is configured to use a slave server. pam_ldap connects to the slave over TLS (as specified in the ldap.conf file) and then gets referred to the master in order to make a change. TLS is never started on the referred connection and pam_ldap attempts to bind in the clear. If the master server is not setup to require TLS on all connections, this may go unoticed, as passwd will function as normal. The only place a client is able to try and start_tls for a referred connection is inside rebind_proc. However, a bug in a sanity check in the openldap code means that openldap considers that TLS has already been started on the referrred connection if it has been started on the first connection (it always checks the first connection, rather than checking the default), and so this won't work. Bugs have been filed on both openldap and pam_ldap: http://www.openldap.org/its/index.cgi/Incoming?id=3791 http://bugzilla.padl.com/show_bug.cgi?id=210 This issue also affects nss_ldap, the patch is located here: http://bugzilla.padl.com/show_bug.cgi?id=211
Comment 1 Josh Bressers 2005-07-05 14:20:38 UTC
This issue should also affect FC3
Comment 2 Christian Iseli 2007-01-22 10:14:56 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
Comment 3 petrosyan 2008-02-17 21:08:06 UTC
Fedora Core 4 is no longer maintained. Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the current Fedora release, please reopen this bug and assign it to the corresponding Fedora version.