LDAP Info Exposure Check
Reviews LDAP attributes for sensitive information accessible to authenticated users, including account descriptions, informational fields, and password attributes.
Prerequisite
Requires a valid Standard User account (authenticated).
Commands run
ad-kit runs several NetExec modules to collect account attributes:
nxc ldap <dc_ip> -u <username> -p <password> -M get-desc-users
nxc ldap <dc_ip> -u <username> -p <password> -M get-info-users
nxc ldap <dc_ip> -u <username> -p <password> -M get-userPassword
nxc ldap <dc_ip> -u <username> -p <password> -M get-unixUserPassword
What it checks
ad-kit collects account attributes:
get-desc-users- thedescriptionattribute.get-info-users- the informational fields on user objects.get-userPassword- theuserPasswordattribute.get-unixUserPassword- theunixUserPasswordattribute.
Values are compared against a list of sensitive keywords (password, secret, credential, token, VPN, SSH, RDP, SQL, and similar).
How it works
Administrators sometimes leave operational notes in the description and
info fields that include passwords, account details, or infrastructure
information. The userPassword and unixUserPassword attributes can expose
password or hash values to authenticated users depending on the directory
configuration and its access controls.
Why it matters
Sensitive LDAP information supports credential discovery and shortens the path from a foothold to further access, particularly where password material is exposed directly.
Findings
| Finding ID | Title |
|---|---|
| LDAPINFO-001 | Sensitive Information Stored in LDAP Attributes |
| LDAPINFO-002 | Password Data Stored in LDAP Attributes |
Tooling
- NetExec: used by this check.
- ldapsearch-ad: LDAP enumeration.