Bug 458187 - RFE: limiting Directory Manager (nsslapd-rootdn) bind access by source host (e.g. 127.0.0.1)
Summary: RFE: limiting Directory Manager (nsslapd-rootdn) bind access by source host (...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Security - Access Control (ACL)
Version: 1.1.1
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL: https://www.redhat.com/archives/fedor...
Whiteboard:
Keywords:
Depends On:
Blocks: 389_1.3.0 512820 690319
TreeView+ depends on / blocked
 
Reported: 2008-08-06 21:56 UTC by Aleksander Adamowski
Modified: 2018-11-27 20:56 UTC (History)
7 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-03-04 23:31:00 UTC


Attachments (Terms of Use)

Description Aleksander Adamowski 2008-08-06 21:56:41 UTC
Description of problem:

The Directory Manager account (the one whose DN is specified in dse.ldif as nsslapd-rootdn) is a dangerously privileged account.

Access control does not apply to this user and compromising its DN and password gives full control over the directory server.

Therefore, it would be desirable to limit this user's bind access based on some additional criteria, in addition to the knowledge of the password.

Limits based on the source host (e.g. localhost) and/or time of day (e.g. only work hours) would be very useful. 

Currently an attacker can easily mount a brute force guessing attack on the Directory Manager account over the network and if he succeeds, he practically has full control over the directory server. The only defense against this is by using a very long manager password and hard to guess rootdn which may be somewhat unpractical.

This problem is especially significant for LDAP servers accessible from public networks.

Additional info:

Note that in OpenLDAP this is possible using the following ACL:

access to dn.base="cn=Manager,o=Example"
 by peername.regex=127\.0\.0\.1 auth
 by users none
 by anonymous none


This ACL however requires creating a concrete LDAP entry that corresponds to rootdn, setting a userPassword in taht entry, and leaving the rootpw in OpenLDAP configuration undefined. This way the concrete userPassword is used when binding and is subject to that ACL which only allows access from connections that origin from 127.0.0.1.

More details:
http://www.openldap.org/faq/data/cache/761.html
http://www.openldap.org/lists/openldap-software/200711/msg00342.html

Comment 2 Iain Morgan 2011-12-07 20:37:57 UTC
Note that this issue is also relevant to replication manager DNs.

In some cases, it might also be desirable to limit binds to the root DN based on connect type. For example, limit the binds to LDAPI connections.

Comment 3 Martin Kosek 2012-01-04 13:43:21 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/110

Comment 6 Nathan Kinder 2013-03-04 23:31:00 UTC
This was fixed in 389-ds-base-1.2.11.5-1.fc17.  Closing.


Note You need to log in before you can comment on or make changes to this bug.