Certighost Exploit Lets Low-Privileged Active Directory Users Impersonate a Domain Controller
The Certighost exploit allows low-privileged Active Directory users to impersonate a Domain Controller by abusing an improper authorization flaw in the AD CS enrollment "chase" fallback mechanism. By manipulating the `cdc` and `rmd` attributes, attackers can trick the Certificate Authority into signing a certificate for a target Domain Controller, enabling full domain compromise via DCSync. Microsoft patched the vulnerability as CVE-2026-54121 (CVSS 8.8) on July 14, adding validation to ensure t
Analysis
TL;DR
- The Certighost exploit allows low-privileged Active Directory users to impersonate a Domain Controller by abusing an improper authorization flaw in the AD CS enrollment "chase" fallback mechanism.
- By manipulating the
cdcandrmdattributes, attackers can trick the Certificate Authority into signing a certificate for a target Domain Controller, enabling full domain compromise via DCSync. - Microsoft patched the vulnerability as CVE-2026-54121 (CVSS 8.8) on July 14, adding validation to ensure the chase target is a legitimate DC before proceeding with enrollment.
- The public proof-of-concept demonstrates that exploitation requires no admin rights or user interaction, relying instead on default configurations like the MachineAccountQuota and standard Enterprise CA setups.
Why It Matters
This vulnerability highlights a critical intersection between identity management and certificate infrastructure, demonstrating how default configuration settings (like machine account quotas) can be leveraged for severe privilege escalation. For security practitioners, it underscores the importance of auditing Active Directory Certificate Services (AD CS) configurations and understanding the trust relationships between CAs and Domain Controllers. The ease of exploitation without administrative privileges makes this a high-risk threat for any organization maintaining an Enterprise CA environment.
Technical Details
- Vulnerability Mechanism: The flaw resides in the AD CS "chase" fallback, where the CA contacts an Active Directory server specified by the requester (
cdc) to resolve machine object information (rmd). The CA failed to verify that the providedcdcwas a genuine Domain Controller before accepting its response. - Exploitation Chain: Attackers create or reuse a computer account (leveraging the default
ms-DS-MachineAccountQuotaof 10), run rogue LSA/LDAP listeners, and relay the CA's authentication challenge to the real DC over Netlogon. This allows them to inject the target DC'sobjectSidanddNSHostNameinto a certificate request. - Post-Exploitation Impact: The resulting certificate enables PKINIT authentication as the Domain Controller. This grants the attacker the ability to perform DCSync attacks to retrieve the
krbtgthash and other account secrets, effectively compromising the entire domain. - Mitigation and Patching: Microsoft’s patch adds
CRequestInstance::_ValidateChaseTargetIsDCtocertpdef.dll, which validates that the chase target matches a specific AD computer object withSERVER_TRUST_ACCOUNTflags and blocks IP literals or metacharacters. An interim mitigation involves disabling the chase flag viacertutil -setreg policy\EditFlags -EDITF_ENABLECHASECLIENTDC.
Industry Insight
Organizations must immediately verify if their Enterprise CA hosts are running the July 14 Microsoft updates, as the public availability of the exploit increases the likelihood of active targeting. Security teams should audit their AD CS policies to determine if the "chase" feature is necessary; if not, disabling it provides immediate risk reduction while patching is applied. Additionally, reviewing and potentially lowering the MachineAccountQuota or restricting computer account creation permissions can mitigate the initial foothold required for this attack chain.
Disclaimer: The above content is generated by AI and is for reference only.