User Account Control (UAC) Bypass Techniques
You'll learn how attackers escalate privileges on Windows by exploiting UAC's design weaknesses and trusted system paths.
What is UAC Bypass?
User Account Control (UAC) is Windows' mechanism to prevent unauthorized changes by prompting for elevation. However, UAC isn't a true security boundary—Microsoft acknowledges that a standard user with admin credentials can bypass it. UAC bypass techniques exploit this design to gain elevated privileges without triggering prompts, crucial for post-exploitation when you've already compromised a user account.
Core Bypass Methods
Auto-Elevation Exploitation
Windows automatically elevates certain trusted Microsoft-signed binaries without prompting. Attackers identify these binaries (like fodhelper.exe, eventvwr.exe) and manipulate registry keys or environment variables they read. When the trusted binary launches, it inadvertently executes attacker-controlled code with elevated privileges.
Analogy: Imagine a VIP entrance that doesn't check guests' bags because they're "trusted." You slip something in a VIP's bag, and it passes through unchecked.
DLL Hijacking for Elevation
Auto-elevated binaries often load DLLs without specifying full paths. By placing a malicious DLL in a search path location the binary checks before System32, you hijack the load order. The elevated process loads your DLL, granting you high-integrity execution.
Trusted Binary Abuse
Legitimate Windows utilities designed for system management may have flawed implementations. For example, binaries accepting file paths or commands without proper validation can be tricked into executing arbitrary payloads with their elevated context.
Detection and Defense
Monitor registry modifications in auto-elevate locations, unusual parent-child process relationships (like fodhelper.exe spawning cmd.exe), and file writes to system directories by non-admin users.
Key Takeaway: UAC bypass exploits trust relationships in Windows through auto-elevation abuse, DLL hijacking, and trusted binary manipulation—requiring defenders to monitor process behavior and registry changes for anomalies.