ESC1
Modifiable SAN + Smart Card Logon or Client Authentication or PKINIT Client Authentication EKUs
The vulnerable certificate template allows requesters to specify a SAN in the CSR as well as allows Smart Card Logon (1.3.6.1.4.1.311.20.2.2) or Client Authentication (1.3.6.1.5.5.7.3.2) or PKINIT Client Authentication (1.3.6.1.5.2.3.4) EKUs.
Enumerate
Find template with this misconfiguration with native Active Directory module:
PS > Get-ADObject -LDAPFilter '(&(objectclass=pkicertificatetemplate)(!(mspki-enrollment-flag:1.2.840.113556.1.4.804:=2))(|(mspki-ra-signature=0)(!(mspki-ra-signature=*)))(|(pkiextendedkeyusage=1.3.6.1.4.1.311.20.2.2)(pkiextendedkeyusage=1.3.6.1.5.5.7.3.2) (pkiextendedkeyusage=1.3.6.1.5.2.3.4))(mspki-certificate-name-flag:1.2.840.113556.1.4.804:=1))' -SearchBase 'CN=Configuration,DC=megacorp,DC=local'Disable the KB5014754 Patch
Disable szOID_NTDS_CA_SECURITY_EXT extension checking (requires CertSvc restart):
Cmd > certutil.exe -setreg policy\DisableExtensionList +1.3.6.1.4.1.311.25.2Exploit
Certutil
Certify
Request a certificate specifying the /altname as a domain admin:
Convert .pem to a .pfx certificate:
Request a TGT with the .pfx certificate:
Certipy
Enroll a certificate with privileged subject in SAN:
Request TGT providing the certificate and get the corresponding NT hash automatically:
Manually via web enrollment at /certsrv/certrqxt.asp:
certi
Enroll a certificate with privileged subject in SAN:
Request TGT providing certificate:
Request NT hash providing TGT or DCSync:
Last updated