Microsoft is testing an optional Lockdown Mode in Edge Canary that blocks websites from using the WebGL, WebGL2 and WebGPU graphics interfaces. The aim is to reduce exposure to attacks involving the browser’s GPU process, according to reports from BleepingComputer and Neowin. SourceSource
The catch: games, maps and other sites relying on those graphics interfaces may stop working properly, BleepingComputer reports. Source
This is a trade-off for people facing targeted attacks, rather than a recommendation to crank every browser security setting to maximum. Microsoft doesn’t consider the compatibility cost desirable for regular users, according to Neowin. Source
“Lockdown Mode is designed for users who are at particular risk of being targeted in cybersecurity campaigns,” Microsoft Partner Security Group Manager Gareth Evans said in a blog post quoted by BleepingComputer. He lists journalists, executives, security researchers and administrators among the intended users. Source
Why target graphics?
Lockdown Mode builds on Edge’s Enhanced Security Mode, which disables just-in-time compilation in the V8 JavaScript engine. The new experiment targets another part of a possible attack chain: using the GPU process to gain access beyond normal restrictions or escape the browser’s sandbox, which isolates web content. SourceSource
BleepingComputer quotes Evans describing the GPU process as a more privileged component handling complex graphics work across browser code, third-party libraries and device drivers. Blocking these APIs is intended to cut off routes into that code—not switch off the computer’s graphics card. Source
Microsoft estimates that the current Canary implementation would have prevented almost 60% of privilege-escalation attacks since February 2022, Neowin reports. Source BleepingComputer describes the estimate as covering attacks targeting Edge users in the wild. Source The estimate doesn’t establish a protection rate against future attacks.
How the Canary test works
Neowin describes the following setup for testers in Edge Canary: Source
- Update Canary through
edge://settings/help.
- Open
edge://flags/#edge-sdsm-plus, set the flag to Enabled, and restart.
- Go to
edge://settings/privacy/security, turn on Enhance your security on the web, and select Strict.
- Make sure Block WebGL graphics and Block WebGPU graphics are both enabled. Source
Those two blocking settings default to enabled for profiles that hadn’t previously used Enhanced Security Mode; existing users of that feature currently need to enable them themselves, Neowin reports. This isn’t a browser-wide switch being flipped for everyone. Source
After reloading a test page, a Lockdown Enabled indicator appears in the address bar when WebGL or WebGPU is blocked. Neowin also reports that DevTools console warnings identify blocked requests, giving testers something more useful than a map that has abruptly lost its ambitions. Source
Microsoft expects the full set of protections to take several releases. It says the experiment will inform clearer explanations of restricted capabilities and site-level exceptions for trusted sites. Neowin reports no date for general availability. Source
Comments