Windows SeTakeOwnershipPrivilege Can Enable SYSTEM Escalation Through Accessibility Binaries

· Original article ↗

Summary

A lab tutorial shows how misdelegated SeTakeOwnershipPrivilege can let a standard domain user replace Utilman.exe or osk.exe and obtain SYSTEM access on a Windows domain controller; it also recommends policy restrictions, integrity monitoring, NLA and WDAC.

Key points

  • The lab grants a standard domain user SeTakeOwnershipPrivilege through Group Policy, allowing the user to take ownership of protected files and change their permissions.
  • Replacing Utilman.exe with cmd.exe lets the login-screen accessibility control open a command prompt running as SYSTEM; the demonstration uses it to reset the built-in Administrator password.
  • A second demonstration replaces osk.exe with a reverse-shell payload, which returns a SYSTEM shell when launched from the login screen.
  • The article recommends limiting the privilege to administrators and tightly scoping any operational exceptions.
  • Suggested detection includes auditing ownership and permission changes, monitoring writes to System32, checking binary integrity, and alerting on unusual winlogon.exe child processes.
  • NLA can block the demonstrated remote RDP login-screen path; WDAC and restricting remote-management access to domain controllers are also recommended.

Article Details

Topic
Abuse of SeTakeOwnershipPrivilege to replace Windows accessibility binaries and escalate privileges to SYSTEM

Indicators of compromise

TypeIndicatorContext
IPV4192[.]168[.]1[.]17Kali attacker host configured to receive the reverse-shell callback from the replaced osk.exe in the demonstration.

MITRE ATT&CK

Products

Tools

Related Articles