Windows Sandbox Attack Surface Analysis
Summary: Google Project Zero's James Forshaw released an open-source toolset, under an Apache v2 license, for analyzing the attack surface of Windows user-mode sandboxes by using the kernel's AccessCheck function to determine what resources a sandboxed process token can reach. The suite includes Check* tools for files, devices, registry, processes, network sockets and the object manager, plus utilities such as DumpProcessMitigations, EditSection, GetHandles and TokenViewer, and running it against Chrome's GPU process showed write access to c:\ProgramData\Microsoft\Windows\DRM.
Bottom line: The tools exist because restricted tokens, Mandatory Integrity Labels and LowBox tokens make access checks too complex to replicate by hand, so a sandbox escape can hide in a permission nobody modeled. A write path into a DRM directory from a Chrome GPU process is the kind of finding that turns a sandbox into a stepping stone.
Read the original at Google Project Zero ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026