>Our efforts to work with the Chrome team to add missing APIs were unsuccessful, unfortunately. Currently, it is impossible to use other browsers and get the same level of protections as when using the Tor Browser.
Chromium is a magnitude more secure than Firefox. If you find a 0day in the Firefox renderer, bam, code execution with full user permissions. A 0day in Chromium renderer code is pretty much worthless.
Firefox has zero additional layers of security. Chromium has a battle-tested sandbox which kills 99% of all exploits in the absence of an additional kernel exploit.
Also note how none of the recent Flash 0days was exploitable on Chrome.
"developers of the Tor browser" probably not, lots of incompetent people in infosec. Tor itself has decent devs, but even they have seen leadership troubles recently, pressure from feds etc. Check the mailing-list.
Reminder, this isn't a vulnerability in Tor, but an IP leak in Firefox, or at least the way it's configured in TBB.
Maybe a sandbox is irrelevant to an IP leak though, idk.
Or more importantly, why isn't there a browser written in a language impervious to low level buffer overruns, ROP, and pointer problems?
Certainly there are other higher level data exposure problems that could manifest, but I'm so utterly sick of C-level security exploits that I'm ready to throw everything out with the bathwater.
Yes, zero day exploits are present in all software, that is a known fact (Chrome is not an exception)... in fact, 0-days is just what is publicized... there is the exploits that are kept private which might one day become "0-day".
I'm not sure why anyone uses a big-name browser on tor anymore. It's trivial to lock something like wget or lynx/links into using the tor connection and getting the same kind of results.
A sandbox is necessary, and I'm 100% sure there are a ton of 0-days in all browsers.