Researcher Details Microsoft Edge Sandbox Escape Built from Logic Flaws

· Original article ↗

Summary

Orange Tsai detailed a non-memory-corruption chain using Edge logic flaws to achieve UXSS, escape the sandbox and execute code on Windows. Demonstrated at Pwn2Own Berlin, it was patched in Edge 148.0.3967.70; there is no evidence it was used against real users.

Key points

  • Orange Tsai of DEVCORE demonstrated the chain at Pwn2Own Berlin in May; the exploit later won $175,000.
  • A navigation-throttle logic flaw enabled universal cross-site scripting, while additional Edge weaknesses helped trigger the chain without a click.
  • The chain used Edge’s Immersive Reader to escape the sandbox, then abused a diagnostic-log function to write an attacker-controlled file.
  • It modified a protocol-handler configuration file and used a telnet:// link to launch an attacker-planted program from a user-writable folder.
  • One step read the victim’s email address from assets.msn[.]com because of a misconfigured cross-origin setting.
  • Microsoft fixed the Edge flaws in version 148.0.3967.70 on May 15; the article says there is no evidence the chain was used against real users.

Article Details

Attack Vectors
  • A malicious web page triggers a chain of Edge and Windows logic flaws, producing universal cross-site scripting that can run JavaScript on any website and bypass content security policy.
  • The exploit uses Edge's conditional access navigation throttle and a second-window popup path to trigger navigation in the browser's own process without a click.
  • Edge's Immersive Reader runs under a read:// address that was not barred from running scripts; the chain uses this to call an internal diagnostic-log function and write an attacker-chosen file anywhere on disk.
  • The chain overwrites a configuration file controlling which websites may launch protocol handlers, restarts Edge, and launches a telnet:// link. Windows searches the system path and runs an attacker-planted copy from a folder writable by a low-privileged user.
Defensive Notes
  • Microsoft fixed the Edge bugs on May 15 in Edge Stable version 148.0.3967.70; updating Edge closes the chain.
  • The article reports no evidence that the competition exploit was used against real users. It says up-to-date browsers are not at risk.

MITRE ATT&CK

CVE

People

Vendors

Products

Related Articles