AS-REP Roastable Accounts
Accounts with Kerberos pre-authentication disabled let anyone request data encrypted with a key derived from the account's password and crack it offline.
| Severity | High |
| CVSS 3.1 | 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Open in the calculator |
| CVSS 4.0 | 9.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-304: Missing Critical Step in Authentication |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1558.004 AS-REP Roasting, T1110.002 Password Cracking, T1078.002 Domain Accounts |
| Category | Security Misconfiguration |
Description
One or more accounts have Kerberos pre-authentication disabled, shown by the DONT_REQ_PREAUTH flag (0x400000) in the userAccountControl attribute and by the Do not require Kerberos preauthentication option in Active Directory Users and Computers. Normally a client must prove that it knows the password, by encrypting a timestamp with its key, before a domain controller issues a ticket-granting ticket. Without pre-authentication, the domain controller answers a request for the account from anyone, and part of its reply (the AS-REP) is encrypted with a key derived from the account's password.
An attacker on the internal network can therefore obtain the reply and attack it offline to recover the password, a technique known as AS-REP roasting, without triggering account lockout. No credentials are needed to request it, only the account name and network access to a domain controller, although any authenticated user can list every affected account with a single LDAP query. If the password is weak, the attacker gains the account and everything it can access; where the account is privileged or used by a service, this can lead to compromise of servers or of the domain. A long, random password makes cracking impractical, but the setting still removes a protection that otherwise applies to every account.
The setting is usually found on accounts created for legacy applications or Kerberos implementations that did not support pre-authentication, or where it was changed during troubleshooting and never restored. An attacker who can write to an account's userAccountControl attribute can also set it deliberately. Impacket's GetNPUsers.py, Rubeus and NetExec identify affected accounts and retrieve replies that hashcat (mode 18200) can attack, and BloodHound and PingCastle report the flag.
Remediation
- List the affected accounts and confirm with each owner whether any system genuinely depends on the setting. Current Windows, Linux and macOS Kerberos clients support pre-authentication, so a genuine dependency is rare.
- Re-enable pre-authentication by clearing Do not require Kerberos preauthentication on the Account tab in Active Directory Users and Computers, or with the ActiveDirectory PowerShell module as shown below.
- Reset the password of every affected account, since its reply may already have been captured, and give any account that must keep the setting a long, random password.
- Check for the flag regularly as part of directory monitoring, since it can be set again by an administrator or by an attacker preparing an account for roasting.
Run the first command to review the accounts before running the second. Confirm the fix by repeating the query and requesting an AS-REP for each previously affected account, which should now fail with a pre-authentication required error.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.