01Description
Domain controllers did not require LDAP signing or LDAPS channel binding.
02Impact
Attackers can relay captured authentication to LDAP to modify Active Directory, for example by creating computer accounts or configuring delegation, as a step towards privilege escalation.
03Severity
Typically
Medium
Typically Medium. Medium alone. High when combined with coercion or IPv6 DNS takeover, which allow authentication to be relayed to LDAP.
04How to verify
- 1Check domain controller policy for LDAP server signing requirements and channel binding settings.
- 2Test unsigned LDAP binds and LDAPS without channel binding using a standard user.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Require LDAP signing and set LDAP channel binding to 'Always' on domain controllers, after auditing clients using event logs.
- 2Combine with SMB signing and disabling LLMNR to reduce relay opportunities.
06References
Draft findings like this from your own evidence
Book a demo