How Misconfigured SeDebugPrivilege Enables Windows Domain Controller Privilege Escalation

· Original article ↗

Summary

A lab walkthrough demonstrates how granting a standard domain user SeDebugPrivilege can enable LSASS credential extraction or SYSTEM token abuse on a Windows Domain Controller, and outlines Group Policy, LSA Protection, Credential Guard, and monitoring defenses.

Key points

  • The lab assigns the Debug programs right through Group Policy to a standard domain user on a Windows Domain Controller.
  • ProcDump creates an LSASS dump; pypykatz recovers an active Administrator session's NTLM hash, which the walkthrough uses to access the Domain Controller as Domain Administrator.
  • In the demonstration, Meterpreter migration into winlogon.exe yields a SYSTEM session.
  • SeDebugPrivesc duplicates a SYSTEM process token to spawn a command shell or reverse shell.
  • The article recommends restricting Debug programs to Administrators and auditing Group Policy assignments.
  • Suggested defenses include LSA Protection, Credential Guard, and an Attack Surface Reduction rule to block credential-stealing reads from LSASS.
  • Suggested detection opportunities include ProcDump targeting LSASS, suspicious writes to winlogon.exe, unusual child processes or outbound connections, and token duplication.

Article Details

Topic
Abuse of SeDebugPrivilege for Windows privilege escalation on a Domain Controller

Indicators of compromise

TypeIndicatorContext
IPV4192[.]168[.]1[.]17Attacker-controlled Kali lab host used as the reverse-shell callback address in the demonstrated payloads.

MITRE ATT&CK

People

Vendors

Products

Tools

Related Articles