~/d4nnyX

← CPTS

Active Directory Enumeration & Attacks

Active Directory · CPTS

  • Active Directory
  • BloodHound
  • Kerberos

The idea

Active Directory is the heart of most enterprise engagements. With even one low-privileged account I can read most of the directory, and the goal is to turn that visibility into a path of abusable relationships that ends at Domain Admin.

How I work through it

Map first. I collect the whole graph and let BloodHound find the shortest path, rather than guessing:

bloodhound-python -d corp.local -u user -p pass -c All -ns 10.10.10.10

Roast for credentials. Kerberoasting pulls crackable service-account hashes; AS-REP roasting targets accounts without pre-auth:

GetUserSPNs.py corp.local/user:pass -request -dc-ip 10.10.10.10
GetNPUsers.py corp.local/ -usersfile users.txt -no-pass -dc-ip 10.10.10.10

Follow the graph. BloodHound surfaces abusable ACLs (GenericAll, WriteDACL), delegation, and admin sessions. I chain those edges — e.g. reset a password I control, then use that account's rights — and once I have replication rights I pull the krbtgt hash with DCSync.

Pitfalls I watch for

  • Clock skew breaks Kerberos. If tickets fail, I sync time to the DC (ntpdate/faketime) before debugging anything else.
  • BloodHound shows what is possible, not what is safe — I read each edge's abuse info rather than running tooling blind.
  • Service accounts with weak passwords are the usual first win; a strong 25-character service password quietly closes the easiest door.

Takeaway

AD is a graph problem. Collect it fully, roast for an initial credential, then walk the relationships — the path to Domain Admin is almost always already drawn, waiting to be read.