kerberoasting
Kerberoasting
Methodology
Enumerate what user account running as a service account we want to kerberoast.
Make sure it's not a honey pot account.
Make sure is a user made account, we don't want machine accounts since they have long passwords.
If OPSEC is needed kerberoast RC4-only accounts and add a delay between requesting tickets.
Kerberoast the user account.
Make sure we get back a RC4 hash and not an AES256 hash.
Crack the ticket.
Powershell
[!INFO] Remember to follow the Powershell methodology
PowerView
Find users that have an SPN set
Get-DomainUser -SPN | select cn, serviceprincipalnameFind users that have an SPN set and are RC4-only
Request a ticket with SPN
Request a ticket with account name
Get all SPN account hashes. WARNING: EXTREMELY NOSIY!
ActiveDirectory module
Find users that have an SPN set
Binaries
[!INFO] Remember to follow the binaries methodology
Rubeus
Request a ticket
RC4-Only account (Avoids downgrade detection, skips AES supported tickets)
Get all SPN account hashes. WARNING: EXTREMELY NOISY!
Ticket Cracking
https://www.openwall.com/john/k/john-1.9.0-jumbo-1-win64.zip
Targeted Kerberoasting
If we have sufficient rights (GenericAll/GenericWrite), a target user's SPN can be set to anything (unique in the domain) instead of changing the password.
Methodology
Check if we have Generic All/Generic Write over another user by checking groups it belongs to.
Check if the user already has an SPN.
Set the SPN.
Kerberoast the user account.
Make sure we get back a RC4 hash and not an AES256 hash.
Crack the ticket.
Search for GenericAll/GenericWrite:
Check if the user has an SPN
Set the SPN
Request the ticket
Crack the ticket
Last updated