FF Sandbox Escape
11–20 of 26 posts
Re: FF Sandbox Escape
#12Re: FF Sandbox Escape
#13It looks like this is not an actual exploit, but a hole in the sandbox that first requires injecting custom code into the process?
Re: FF Sandbox Escape
#14Re: FF Sandbox Escape
#15Re: FF Sandbox Escape
#16It looks like this is not an actual exploit, but a hole in the sandbox that first requires injecting custom code into the process?
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.
Re: FF Sandbox Escape
#17Meh...escape must mean something different at Google
Re: FF Sandbox Escape
#18It looks like this is not an actual exploit, but a hole in the sandbox that first requires injecting custom code into the process?
Re: FF Sandbox Escape
#19> As I’m a Chromium committer as well as an owner of the Windows sandbox I realized I might be better placed to fix this than Mozilla who relied on our code.
Re: FF Sandbox Escape
#20Off topic, does Firefox depend on Chromium code? > As I’m a Chromium committer as well as an owner of the Windows sandbox I realized I might be better placed to fix this than Mozilla who relied on our code.