Kerberoastable Service Accounts

User accounts with service principal names can have their Kerberos service tickets requested by any domain user and cracked offline to recover weak passwords.

SeverityHigh
CVSS 3.17.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.07.7 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-521: Weak Password Requirements
OWASP Top 10A07:2025 Authentication Failures
MITRE ATT&CKT1558.003 Kerberoasting, T1110.002 Password Cracking, T1078.002 Domain Accounts
CategorySecurity Misconfiguration

Description

One or more user accounts in the domain have a service principal name (SPN) registered, which allows any authenticated domain user to request a Kerberos service ticket for them. Part of each service ticket is encrypted with a key derived from the account's password, so a ticket can be taken offline and attacked to recover the password, without further contact with a domain controller and without triggering account lockout. The technique is known as Kerberoasting.

Any domain user, or an attacker who controls any domain account or domain-joined computer, can request tickets for every Kerberoastable account and attempt to crack them at leisure. The ticket requests resemble normal Kerberos traffic, although a burst of requests, particularly for RC4 tickets, can be detected. Where a password is recovered, the attacker gains every right the account holds, which commonly includes administrative access to the servers that run the service and to its data and, where the account is in a privileged group, control of the domain.

The risk depends on the strength of the password and on the encryption type. Service account passwords are often chosen by a person, set once and never changed. Where an account still accepts RC4, an attacker requests an RC4-encrypted ticket, whose key is the account's NT hash and which can be tested at very high speed; AES-encrypted tickets are slower to attack but still fall to a weak password, while long, randomly generated passwords and AES-only encryption make cracking impractical.

Kerberoastable accounts can be listed with an LDAP query for user objects that have a servicePrincipalName value, and tools such as Impacket's GetUserSPNs.py, Rubeus and NetExec request the tickets in a form that hashcat (modes 13100, 19600 and 19700) can attack. BloodHound and PingCastle report these accounts and highlight those with privileged group membership. Computer accounts and managed service accounts also have SPNs but have long random passwords, so they are not practical targets.

Remediation

  • Replace service accounts with group managed service accounts (gMSAs) wherever the application supports them. Windows generates and rotates their passwords automatically, every 30 days by default, so they cannot practically be cracked.
  • Where a user account must remain, give it a long, randomly generated password stored in a vault: Microsoft recommends at least 14 characters for service accounts, and considerably more is practical because nobody needs to type it. Change it after any suspected exposure.
  • Configure remaining service accounts to use AES only, by setting msDS-SupportedEncryptionTypes (for example through the AES options on the Account tab in Active Directory Users and Computers), and then reset the password so that AES keys exist. Test first: systems that support only RC4 will fail to authenticate to the service.
  • Remove SPNs that are no longer needed, and remove service accounts from privileged groups, granting only the rights each service needs.

As an interim measure, change the passwords of privileged service accounts and of those with the oldest pwdLastSet values first. Monitor domain controllers for unusual volumes of service ticket requests (event 4769), especially with ticket encryption type 0x17 (RC4). Confirm the fix by requesting the tickets again and checking that none can be cracked against a large wordlist and rule set.

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 trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Active Directory Findings

Every Active Directory finding