~/d4nnyX

← CPTS

Windows Privilege Escalation

Privilege Escalation · CPTS

  • Privilege Escalation
  • Windows
  • SYSTEM

The idea

Windows privilege escalation follows the same enumerate-then-abuse rhythm as Linux, but the wins live in different places: token privileges, service misconfigurations, and the many spots Windows stores credentials.

How I work through it

Enumerate context and privileges first:

whoami /priv
whoami /groups
.\winPEASany.exe

Check the high-value paths:

  • Token privileges — SeImpersonate or SeAssignPrimaryToken (common on service accounts) leads to SYSTEM via a Potato-style attack.
  • Service misconfigurations — unquoted service paths, weak service permissions, or a writable service binary.
  • Stored credentials — the SAM and SYSTEM hives, unattended install files, saved RDP/Windows Credential Manager entries, and registry autologon keys.

With admin access I dump hashes from LSASS or the SAM, which both escalates and feeds lateral movement across the domain.

Pitfalls I watch for

  • whoami /priv is the first thing I read — a single enabled privilege often replaces a long hunt.
  • Match the tooling to the Windows build and architecture; a token-abuse exploit that fits the version matters more than the newest one.
  • Hashes recovered here rarely stop at this host — I test them across the network before treating the box as finished.

Takeaway

On Windows the fast routes are privileges and services, and credentials are scattered everywhere. Read whoami /priv, enumerate services, loot for secrets, and SYSTEM usually follows.