Off 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.
[deleted]
FF Sandbox Escape
21–26 of 26 posts
Re: FF Sandbox Escape
#22Off 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.
Firefox uses some of the chromium code/libraries for the sandboxing on Windows.
Re: FF Sandbox Escape
#23Off 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.
My one run-in with this has been that Firefox and Chromium both use libwebrtc, which is managed by the Chromium project as far as I can tell.
Re: FF Sandbox Escape
#24It looks like this is not an actual exploit, but a hole in the sandbox that first requires injecting custom code into the process?
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.
Re: FF Sandbox Escape
#25Off 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.
Firefox uses some of the chromium code/libraries for the sandboxing on Windows. https://wiki.mozilla.org/Security/Sandbox/Specifics
I thought one of the main point of Firefox would be to not do this :D
Re: FF Sandbox Escape
#26Earlier quoted context omitted.
Firefox uses some of the chromium code/libraries for the sandboxing on Windows. https://wiki.mozilla.org/Security/Sandbox/Specifics
I thought one of the main point of Firefox would be to not do this :D
Chromium contains a really solid implementation of OS process sandboxing, which is rather secondary to the bits of building a web browser that we need competition on. It could very reasonably be spun out into its own project, but that takes time and effort so it stays part of Chromium.