REDHAT-BUG-676876: Low severity 389 Project 389 vulnerability
Andrew Kerr reported that a 389 replica would crash when an empty modify request is sent to it. This can only happen if the 389 server is built with mozldap (not OpenLDAP) and the modify operation is replicated or the server set 'cn=config nsslapd-lastmod: off'.
389 on Fedora 14 and later, as well as Red Hat Enterprise Linux 6, use OpenLDAP, not mozldap, and are thus unaffected. This flaw does not affect Red Hat Directory Server 8.2.
This flaw was caused by the fix for bug #305131 which allowed empty modify operations to proceed through the code.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-676876?
The severity of REDHAT-BUG-676876 is classified as medium due to the potential for the server to crash with an empty modify request.
How do I fix REDHAT-BUG-676876?
To fix REDHAT-BUG-676876, reconfigure your 389 server to prevent empty modify requests or switch to using OpenLDAP instead of mozldap.
Who reported REDHAT-BUG-676876?
REDHAT-BUG-676876 was reported by Andrew Kerr.
Which versions of 389 are affected by REDHAT-BUG-676876?
REDHAT-BUG-676876 affects 389 servers built with mozldap and specifically those running Fedora 14 and later.
Under what conditions does REDHAT-BUG-676876 occur?
REDHAT-BUG-676876 occurs when an empty modify request is sent to a 389 replica that is either in replication or has 'cn=config nsslapd-lastmod: off' set.