Re:FF Sandbox Escape
by etaioinshrdlu on Thursday June 18, 2020 @07:32PM
(#23569335)
It looks like this is not an actual exploit, but a hole in the sandbox that first requires injecting custom code into the process?
[ Parent
| on HN ]
Re:FF Sandbox Escape
by albntomat0 on Thursday June 18, 2020 @07:49PM
(#23569455)
I guess it depends on how you define "exploit." I'd personally consider bypassing the sandbox an exploit, even though it's not a full chain.
It’s an proof of concept exploit for a vulnerability in the sandbox used by FF which is a security boundary to reduce the impact of RCE. The reason for the injection is I don’t just have a working RCE lying around (we get them fixed) and using one would add additional complications and obfuscate the bug when reporting. The purpose of a proof of concept is to demonstrate impact so that it can be fixed.
All the big browser attacks require exploit chains, and this is a component for creating an exploit chain. The best exploit chains can go all the way from a web page's JS to complete root access (this was achieved on Chromebooks at one point in the last couple years, using webassembly as one of the hops in the chain)
In the end the sandbox is there to provide some limited security even in presence of other vulnerabilities.
So I would say it's a security critical bug a sandbox escape and a building blog for an exploit but not a exploit by itself.
Anyway it's sill a security vulnerability.