Skip to content
StrikeOps

Kerberoastable Service Accounts

HighTypical severity Active DirectoryCWE-521ATT&CK T1558.003

01Description

User accounts with Service Principal Names (SPNs) were identified in Active Directory. Any authenticated domain user can request a Kerberos service ticket for these accounts, part of which is encrypted with the account's password hash, and attempt to crack it offline.

02Impact

Service accounts often have weak or never-changed passwords and elevated privileges. Cracking a service ticket gives the attacker the account's password, which frequently provides administrative access to servers or, where the account is highly privileged, the entire domain.

03Severity

Typically

High

Typically High. High when any Kerberoastable account has a crackable password or privileged group membership. Medium if all affected accounts have long random passwords or use gMSAs.

04How to verify

  1. 1Enumerate user accounts with SPNs using a standard domain user, for example with Impacket's GetUserSPNs.
  2. 2Request service tickets and attempt offline cracking against a wordlist within the agreed time window.
  3. 3Record privileged group membership of each affected account.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Use group Managed Service Accounts (gMSAs) where possible, which have automatically rotated 120-character passwords.
  2. 2Otherwise set long (25+ character) random passwords on service accounts and rotate them.
  3. 3Remove unnecessary SPNs and privileged group membership from service accounts.
  4. 4Enforce AES encryption for Kerberos and monitor for unusual volumes of service ticket requests.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo