AS-REP Roasting
https://attack.mitre.org/techniques/T1558/004/
Last updated
Was this helpful?
https://attack.mitre.org/techniques/T1558/004/
Last updated
Was this helpful?
ATT&CK ID:
Permissions Required: Valid Domain Account | None
Description
Adversaries may reveal credentials of accounts that have disabled Kerberos preauthentication by Password Cracking Kerberos messages.
Preauthentication offers protection against offline Password Cracking. When enabled, a user requesting access to a resource initiates communication with the Domain Controller (DC) by sending an Authentication Server Request (AS-REQ) message with a timestamp that is encrypted with the hash of their password. If and only if the DC is able to successfully decrypt the timestamp with the hash of the user’s password, it will then send an Authentication Server Response (AS-REP) message that contains the Ticket Granting Ticket (TGT) to the user. Part of the AS-REP message is signed with the user’s password.
For each account found without preauthentication, an adversary may send an AS-REQ message without the encrypted timestamp and receive an AS-REP message with TGT data which may be encrypted with an insecure algorithm such as RC4. The recovered encrypted data may be vulnerable to offline Password Cracking attacks similarly to Kerberoasting and expose plaintext credentials.
An account registered to a domain, with or without special privileges, can be abused to list all domain accounts that have preauthentication disabled by utilizing Windows tools like PowerShell with an LDAP filter. Alternatively, the adversary may send an AS-REQ message for each user. If the DC responds without errors, the account does not require preauthentication and the AS-REP message will already contain the encrypted data.
Cracked hashes may enable Persistence, Privilege Escalation, and Lateral Movement via access to Valid Accounts.
AS-REP Roasting takes advantage of Active Directory user accounts that have the option Do not require Kerberos preauthentication enabled.
When this option is enabled we are able to request data from the Active Directory account that is encrypted with the users password. We can take this hash and if successful with cracking, we are able to derive the user accounts password.
Ensure where possible Domain accounts do not have theDo not require Kerberos preauthentication option in Active Directory enabled.
ensure accounts have exceptionally long passwords and are rotated frequently
If possible use a stronger encryption standard rather than RC4.
Audit accounts for which this option is enabled:
URL:
URL:
URL:
URL:
