ASREProast
Theory
The Kerberos authentication protocol works with tickets in order to grant access. A ST (Service Ticket) can be obtained by presenting a TGT (Ticket Granting Ticket). That prior TGT can be obtained by validating a first step named "pre-authentication" (except if that requirement is explicitly removed for some accounts, making them vulnerable to ASREProast).
The pre-authentication requires the requesting user to supply its secret key (DES, RC4, AES128 or AES256) derived from the user password. Technically, when asking the KDC (Key Distribution Center) for a TGT (Ticket Granting Ticket), the requesting user needs to validate pre-authentication by sending a timestamp encrypted with it's own credentials. It ensures the user is requesting a TGT for himself. Once validated, the TGT is then sent to the user in the KRB_AS_REP
message, but that message also contains a session key. That session key is encrypted with the requested user's NT hash.
Because some applications don't support Kerberos preauthentication, it is common to find users with Kerberos preauthentication disabled, hence allowing attackers to request TGTs for these users and crack the session keys offline. This is ASREProasting.
While this technique can possibly allow to retrieve a user's credentials, the TGT obtained in the KRB_AS_REP
messages are encrypted cannot be used without knowledge of the account's password.
Practical
Recon
User Enumeration
LDAP
RPCClient
Retrieve Users TGTs
Impacket
Crack Hash
John
Hashcat
Get Shell Access
Evil-Winrm
Evil-Winrm (Docker) - Recommended
REFERENCES
Last updated
Was this helpful?