It was discovered that modify operation with NOOP control on an entry stored in BDB backed can cause OpenLDAP's slapd daemon to crash. Further details and patch can be found in upstream bug / CVS: http://www.openldap.org/its/index.cgi/Software%20Bugs?id=4925 http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/modify.c.diff?r1=1.124.2.16&r2=1.124.2.17&f=h NOOP control was introduced in OpenLDAP 2.1 branch as documented on roadmap page: http://www.openldap.org/software/roadmap.html This issue was fixed upstream in version 2.3.36: http://www.openldap.org/devel/cvsweb.cgi/~checkout~/Attic/CHANGES?rev=1.5.8.414
This issue does not affect OpenLDAP packages as shipped in Red Hat Enterprise Linux 2.1 and 3. OpenLDAP packages in Red Hat Enterprise Linux 4 and 5 are affected and issue will be addressed in the security advisory. Note: On Red Hat Enterprise Linux 5, database recovery performed during slapd daemon startup may not properly clean up after the crash caused by such request with NOOP control. Affected DN may remain locked / unaccessible via LDAP requests. If this occurs, you need to run database recovery manually using following command: slapd_db_recover -v -h /var/lib/ldap while slapd daemon is stopped.
openldap-2.3.34-6.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
This issue was addressed in: Red Hat Enterprise Linux: http://rhn.redhat.com/errata/RHSA-2008-0110.html Fedora: https://admin.fedoraproject.org/updates/F7/FEDORA-2008-1307