When the Sandbox Fails: Local Privilege Escalation as the Bridge From Browser Compromise to Full System Control

The Second Step in the Kill Chain

Browser sandboxes exist for one reason: to ensure that even when code execution happens inside the browser, the attacker remains trapped in a low-privilege container with no meaningful access to the underlying system. This architectural assumption underpins the security model of every major browser and, by extension, the safety of billions of daily web sessions. But a sandbox is only as strong as the kernel it sits on top of. When a local privilege escalation vulnerability exists in a core Windows interprocess communication mechanism, that sandbox becomes a speed bump rather than a wall.

The attackers who chain browser exploits with kernel-level privilege escalation are not opportunists. They are building reliable exploit chains that turn a single malicious webpage visit into complete system compromise. The browser gets them in the door; the kernel bug gives them the keys to everything.

This pattern matters because it inverts the usual advice about "just keep your browser updated." A fully patched browser running on an unpatched Windows kernel is still vulnerable to the two-stage attack: RCE in the browser context, then escape via the kernel. The sandbox assumption breaks when the floor underneath it has a hole.

CVE-2023-21674: The Kernel Side of the Chain

CVE-2023-21674 is the specific instance of this pattern that Microsoft patched in January 2023, and it was already being exploited in the wild when the fix shipped. The vulnerability resides in Windows Advanced Local Procedure Call (ALPC), a kernel-level IPC mechanism that applications use to communicate with system services and each other. The flaw is a use-after-free condition (CWE-416), which allows an attacker with low-privilege code execution to corrupt memory in a way that escalates to SYSTEM-level privileges.

CISA added this vulnerability to the Known Exploited Vulnerabilities catalog on January 10, 2023, the same day Microsoft released the patch. The timing is significant: this was not a theoretical risk discovered by researchers and disclosed responsibly over months. Active exploitation was observed before the patch was available to defenders, making this a true zero-day at the time of discovery. Security researchers have specifically noted its use in browser-based exploit chains, where initial code execution in a sandboxed browser process pivots to full kernel compromise via this ALPC flaw.

The CVSS score of 8.8 reflects the severity: local attack vector, low complexity, low privileges required, no user interaction needed after initial access, and the ability to impact confidentiality, integrity, and availability at the highest level. The "Changed" scope indicator in the CVSS vector confirms that exploitation allows escape from the initial security boundary.

Affected Versions

Patch details:

• January 2023 Patch Tuesday cumulative updates address this vulnerability
• Primary KB articles: KB5022282 (Windows 10), KB5022287 (Windows 11 21H2), KB5022303 (Windows 11 22H2), KB5022291 (Server 2022)
• Full advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21674
• Windows 10 versions 1507 and 1607 have reached or are reaching end of extended support; organizations still running these should plan migration

What This Actually Means If You're Exposed

An attacker who chains this vulnerability with a browser exploit or other initial access vector gains SYSTEM-level privileges on the compromised host. At that point, they own the machine: they can disable security software, dump credentials from LSASS, access all local files regardless of NTFS permissions, install persistent backdoors, and pivot to other systems using harvested credentials or tokens. The attack path goes from "user clicked a link" to "attacker has domain admin potential" in a matter of seconds if credential material is present.

The practical impact depends on what the compromised machine can reach. A workstation with cached domain credentials becomes a launchpad for lateral movement. A system with access to sensitive file shares, databases, or administrative interfaces provides immediate data theft opportunities. Because ALPC is fundamental to Windows operation, there is no practical way to disable or restrict it without breaking the operating system. Every Windows system exposes this attack surface by design.

What To Do About It

1. Apply the January 2023 cumulative update immediately. For Windows 10 22H2, this is KB5022282. For Windows 11 22H2, this is KB5022303. For Windows Server 2022, this is KB5022291. Verify installation via winver or Get-HotFix -Id KB5022282 in PowerShell.

1. Audit systems still running Windows 10 1507 or 1607. These versions have reached or are near end of extended support. Plan upgrades to supported versions to maintain security update coverage for future kernel vulnerabilities.

1. If immediate patching is not possible, implement compensating controls: Restrict local administrator accounts, enforce application allowlisting to limit what code can execute, and segment affected systems away from sensitive network resources. These measures do not prevent exploitation but limit the attacker's ability to capitalize on SYSTEM access.

1. Monitor for post-exploitation indicators. Look for Event ID 4688 (Process Creation) showing unexpected SYSTEM-level process launches, particularly those spawned from browser processes or other low-privilege contexts. Credential dumping attempts may generate Event ID 4656 (handle requests to LSASS). Endpoint detection tools should alert on known post-exploitation tooling such as Mimikatz or Cobalt Strike beacons running with elevated privileges.

1. Review browser security configurations. Ensure browsers are current, and consider enabling hardware-enforced stack protection and other exploit mitigations where supported.

The Sandbox Is Only Half the Story

Attackers think in chains, not individual vulnerabilities. CVE-2023-21674 is valuable precisely because it completes the path from browser compromise to system ownership. Patching browsers without patching the kernel leaves the attack surface half-defended. This vulnerability has confirmed in-the-wild exploitation, is listed in CISA's KEV catalog, and represents the exact class of kernel bug that sophisticated threat actors stockpile for use in targeted operations. Patch immediately; this is not a theoretical risk.