Unconstrained Kerberos Delegation
Hosts other than domain controllers are trusted for unconstrained delegation, so they cache the Kerberos tickets of users who connect and can impersonate them anywhere.
| Severity | High |
| CVSS 3.1 | 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 8.6 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-266: Incorrect Privilege Assignment |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1558 Steal or Forge Kerberos Tickets, T1550.003 Pass the Ticket, T1187 Forced Authentication |
| Category | Security Misconfiguration |
Description
One or more computer or user accounts other than domain controllers are trusted for unconstrained Kerberos delegation, shown by the TRUSTED_FOR_DELEGATION flag (0x80000) in userAccountControl and by the Trust this computer for delegation to any service (Kerberos only) option. When a user authenticates to a service running under such an account, the user's computer sends a copy of the user's ticket-granting ticket (TGT) with the request, and the service keeps it in memory so that it can act as that user towards any other service in the domain. Accounts marked as sensitive, or in the Protected Users group, are not delegated.
Anyone who gains administrative control of the host, or the credentials of the account, can extract and reuse the TGTs of every user who connects to it and so impersonate any of them, including privileged users. The exposure is made worse by authentication coercion: techniques that abuse the Print Spooler (MS-RPRN) or the Encrypting File System Remote Protocol (MS-EFSR, PetitPotam) can make a domain controller authenticate to the host, leaving the domain controller's own TGT in memory. That TGT can be used to replicate every password hash from the directory (DCSync) and so take control of the domain. Exploitation needs that administrative access or the account's credentials first, but the setting turns compromise of one server into compromise of the domain.
The setting can be identified with an LDAP query for the flag, for example with the ActiveDirectory PowerShell module or Impacket's findDelegation.py, and BloodHound and PingCastle report it. Domain controllers are trusted for unconstrained delegation by design and are excluded from this finding.
Remediation
- Remove unconstrained delegation from every account that is not a domain controller. Where a service genuinely needs to act on behalf of users, replace it with constrained delegation to the specific services required, or with resource-based constrained delegation configured on the target, and test the application afterwards.
- Select Account is sensitive and cannot be delegated on privileged accounts, or add them to the Protected Users group, so that their tickets are never delegated.
- Reduce the ways a domain controller can be made to authenticate: disable the Print Spooler service on domain controllers, apply current security updates, and restrict outbound SMB and HTTP connections from domain controllers to the systems they need to reach.
- Until the setting is removed, treat affected hosts as Tier 0: restrict who can administer them and keep privileged accounts from connecting to them.
The following commands list affected accounts other than domain controllers (primary group 516):
Confirm the fix by repeating the query and checking that only domain controllers remain.
References
- learn.microsoft.com/en-us/windows-server/security/kerberos/kerberos-constrained-delegation-overview
- learn.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/protected-users-security-group
- learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/useraccountcontrol-manipulate-account-properties
- cyber.gc.ca/en/news-events/joint-guidance-detecting-and-mitigating-active-directory-compromises
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.