3 ms·
So what happened here? There's an in-the-wild exploit that's bypassing sandboxing - so there must be at least two bugs, or the sandbox isn't tight enough (which
by nneonneo 8y ago
So what happened here? There's an in-the-wild exploit that's bypassing sandboxing - so there must be at least two bugs, or the sandbox isn't tight enough (which, for Chrome, would surprise the hell out of me).
- aboodman 8y agoI used to work on Chrome. There have been periodic sandbox escapes, and chained exploits that escape to userland are routinely performed at pwn2own. This is just notable because there is a live exploit in the wild.
- GordonAitchJay 8y agoThere there any public information about what the live exploit does?
- intherdfield 8y ago"The second vulnerability was in Microsoft Windows. It is a local privilege escalation in the Windows win32k.sys kernel driver that can be used as a security sandbox escape." https://security.googleblog.com/2019/03/disclosing-vulnerabilities-to-protect.html https://security.googleblog.com/2019/03/disclosing-vulnerabi...