CVE-2011-1024: Medium severity red hat openldap servers vulnerability

Published Feb 25, 2011
·
Updated

chain.c in back-ldap in OpenLDAP 2.4.x before 2.4.24, when a master-slave configuration with a chain overlay and ppolicyforwardupdates (aka authentication-failure forwarding) is used, allows remote authenticated users to bypass external-program authentication by sending an invalid password to a slave server.

Other sources

It was reported [1],[2],[3] that in certain configurations, OpenLDAP would authenticate with an invalid password. If an OpenLDAP slave received an authenticated bind request with an invalid password that was forwarded to the master LDAP server, the LDAP slave would return a successful bind (as an anonymous user) rather than return a failure (as the user to authenticate). This is due to a chain overlay being set on the frontend, with a ppolicy configured with ppolicyforwardupdates. While this is not a security issue regarding LDAP contents, due to the authentication as an unprivileged anonymous user, when LDAP returns a successful bind to other external programs (such as programs performing authentication, such as pamldap or SSSD) it could allow a user to login with an invalid password (in that case, if LDAP is used for user authentication, it could lead to a successful login with an invalid password).

This was already corrected upstream [4] for unrelated reasons.

References:

[1] http://www.openldap.org/its/index.cgi/Software%20Bugs?id=6607 [2] http://www.openldap.org/lists/openldap-technical/201004/msg00247.html [3] http://secunia.com/advisories/43331/ [4] http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-ldap/chain.c.diff?r1=1.76&r2=1.77&hideattic=1&sortbydate=0

Red Hat

Affected Software

18 affected components
openldap OpenLDAP=2.4.17
openldap OpenLDAP=2.4.6
openldap OpenLDAP=2.4.11
openldap OpenLDAP=2.4.8
openldap OpenLDAP=2.4.9
openldap OpenLDAP=2.4.16
openldap OpenLDAP=2.4.22
openldap OpenLDAP=2.4.20
openldap OpenLDAP=2.4.15
openldap OpenLDAP=2.4.18
openldap OpenLDAP=2.4.7
openldap OpenLDAP=2.4.23
openldap OpenLDAP=2.4.14
openldap OpenLDAP=2.4.19
openldap OpenLDAP=2.4.12
openldap OpenLDAP=2.4.21
openldap OpenLDAP=2.4.13
openldap OpenLDAP=2.4.10

Event History

Feb 25, 2011
Data Sourced
via Red Hat·04:45 PM
DescriptionSeverityAffected Software
Mar 20, 2011
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-1024?

CVE-2011-1024 has been categorized as having a medium severity due to its potential impact on authentication mechanisms.

2

How do I fix CVE-2011-1024?

To mitigate CVE-2011-1024, upgrade OpenLDAP to version 2.4.24 or later, where the vulnerability has been resolved.

3

Which versions of OpenLDAP are affected by CVE-2011-1024?

CVE-2011-1024 affects OpenLDAP versions prior to 2.4.24, including versions 2.4.6 to 2.4.23.

4

What is the main issue with CVE-2011-1024?

The main issue with CVE-2011-1024 is that it allows remote authenticated users to bypass external-program authentication.

5

Is CVE-2011-1024 exploitability dependent on configuration?

Yes, CVE-2011-1024's exploitability is contingent on using a master-slave configuration with the chain overlay and ppolicy_forward_updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203