First published: Tue Mar 26 2013(Updated: )
It was found that the 389 Directory Server did not properly restrict access to entries when the 'nsslapd-allow-anonymous-access' configuration setting is set to 'rootdse'. An anonymous user could connect to the LDAP database and, if the search scope is set to BASE, obtain access to information outside of the rootDSE. The 'rootdse' option exists to provide anonymous access to the rootDSE but no other entries in the directory. An administrator could believe that directory entries are being restricted with this option enabled, however the information provided would be the same as if 'nsslapd-allow-anonymous-access' were set to 'on'. ACI's are still properly evaluated despite this flaw, so this can easily be mitigated by removing the anonymous read ACL.
Affected Software | Affected Version | How to fix |
---|---|---|
389 Directory Server |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-928105 is considered critical due to potential unauthorized access to sensitive directory information.
To fix REDHAT-BUG-928105, update the 389 Directory Server configuration to restrict anonymous access, particularly adjusting the 'nsslapd-allow-anonymous-access' setting.
REDHAT-BUG-928105 affects multiple versions of the 389 Directory Server where the 'nsslapd-allow-anonymous-access' is misconfigured.
Yes, unauthorized users can exploit REDHAT-BUG-928105 to gain access to sensitive entries in the LDAP database without proper authentication.
An attacker exploiting REDHAT-BUG-928105 can access information about directory entries if the search scope is set to BASE.