5 ms·
Arbitrary code execution through unsanitized browser UI
- sounds 9y agoMods, could we maybe point the URL to the Mozilla Security Advisory? https://www.mozilla.org/en-US/security/advisories/mfsa2018-05/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-0... This bug is fixed in Firefox 58.0.1.
- sctb 9y agoSure thing! We've updated the link from https://tools.cisco.com/security/center/viewAlert.x?alertId=56610 https://tools.cisco.com/security/center/viewAlert.x?alertId=....
- MarkSweep 9y agoThe bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1432966 https://bugzilla.mozilla.org/show_bug.cgi?id=1432966 It sounds like Firefox sometimes injects untrusted HTML into the browser chrome.
- forgotmypw 9y agoAre any of these fixes being backported to 56.x? I am not ready to upgrade to 57+ yet.
- JohnTHaller 9y agoUse Firefox ESR 52.x. Firefox 56 is insecure and should not be used: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/ https://www.mozilla.org/en-US/security/known-vulnerabilities...
- orf 9y agoImmediately stop using 56, downgrade to the LTS or upgrade to 57. 56 is not secure and there are a bunch of vulnerabilities in it. Offtopic: I get the feeling a fair few HN readers don't keep their browsers up to date for whatever reason. It's troubling, seeing as this is a very technical and presumably security-conscious audience.
- danjoc 9y ago>Immediately stop using 56, downgrade to the LTS or upgrade to 57 58 is the fixed version. >I get the feeling a fair few HN readers don't keep their browsers up to date for whatever reason. That's because 57 was a complete dumpster fire. It broke all the add ons. Little wonder people would not update. I was a happy FF user for years. My solution was to dump FF and move on, but I know there are still a lot of people clinging to 56/52 like debris from a shipwreck. Anyone who points this out is granted invisibility powers on HN, so I can see how you would be unaware of this.
- blacksmith_tb 9y agoIt broke add-ons that weren't being maintained, primarily. It's true that for some users, this would be very unpleasant, but I have five extensions working fine here in 59.0b5 (including important security/usability ones like uBlock Origin and Stylus).
- Khoth 9y agoThat's not my experience. The addons I use that it broke were all being maintained, but FF57 didn't provide any API to replace what they were using before, so their authors reluctantly abandoned them or provided limited, crippled versions that don't work properly.
- mastax 9y ago> 58 is the fixed version. FTA: This issue did not affect Firefox for Android or Firefox 52 ESR. > That's because 57 was a complete dumpster fire. I disagree. > It broke all the add ons. Yes, it did. They probably should've made 56 an ESR. > Anyone who points this out is granted invisibility powers on HN, so I can see how you would be unaware of this. They must not be doing a very good job, since I've seen the death of long-loved addons mentioned in every Firefox thread on HN for years.
- geofft 9y agoClinging to 52 ESR until August 28 is fine. That's what it's there for. Clinging to 56 is ... well, it's your decision to use what software you want, that's what free software is all about, but since half the point of the changes in 57 was improved security architecture, clinging to 56 and expecting fixes for security bugs seems ill-advised.
- moosingin3space 9y ago56 will never get backported security fixes of any kind. For the record, neither will 57, as 58 is the current stable version. Mozilla does not apply security fixes to versions of Firefox other than the latest stable and the latest ESR.
- eat_veggies 9y agoDoes this affect the Tor browser's ancient version of Firefox?
- jwilk 9y agoTor Browser is based on Firefox 52 ESR. From the article: This issue did not affect […] Firefox 52 ESR.
- orf 9y agoWell, here is the patch with a relevant test: https://reviewboard.mozilla.org/r/215474/diff/3#index_header https://reviewboard.mozilla.org/r/215474/diff/3#index_header Seems to create an iFrame, sets the source to "chrome://global/content/win.xul", then creates a div (with a NS) inside it and sets the content to: <a onclick="foo()" href="javascript:foo"><script>bar()<\/script>Meh.</a><a href="http://foo/"></a> The expected results is the div contents is: <a>Meh.</a><a href="http://foo/"></a>
- gsnedders 9y agoNah, that test relies on being run with chrome privileges. Firefox refuses to even load such a page within an iframe ordinarily.
- RcouF1uZ4gsC 9y agoWith regards to severe vulnerabilities such as arbitrary code execution, does anyone have an idea of the status of the major browsers (chrome, edge, safari, firefox). What are the relative rankings of these in terms of security?
- quotheth 9y agoThere is no universal metric for security. What I will say is that Edge and Firefox are doing an excellent job - I'm really impressed. Chrome is still the safest browser today, in my opinion. Site isolation, which was released recently, is a really great example of how far ahead they are - site isolation is at least 3, maybe 4 years in the making. That's serious work. They have had an excellent bounty program. They have project 0 doing advanced offensive research, much of which has been relevant to browsers. They fuzz a ton and have managed to solicit others to do the same (not that other browsers don't/ haven't). Their sandbox is incredible and constantly evolving. They basically invented seccomp v2 just to improve their sandboxing stature on linux. They implemented 'forceaslr' before EMET was even a thing to help prevent info leaks from third party libs. Their new kernel32.dll unloading mitigation is awesome, and as far as I know the first instance of such a thing. I could really go on and on, I'm sure - they have taken incredible proactive measures and they're just getting better at it. We can see similar growth in Edge, which has had a sandbox for years. Firefox has more recently gotten a sandbox and the move to rust is encouraging. But... yeah, in my opinion, Chrome takes the cake.
- duozerk 9y agoThis is the kind of advisory that comfort me in my choice to use ESR; browsers are so critical security-wise that it just seems safer. Although if everyone did that nobody would test new features I guess.
- matheist 9y agoHow would an attacker have used this vulnerability? It seems to me that they'd already have to be able to inject code into the chrome context, to be able to point it towards content they control. Maybe I misunderstand how this works.
- deleted 9y ago[deleted]
- riccardoforina 9y agoIt's funny though how a security related page is insecure because of a misconfigured third party js. https://imgur.com/a/CBftH https://imgur.com/a/CBftH https://sslanalyzer.comodoca.com/?url=https%3A%2F%2Fadmin.brightcove.com%2Fjs%2FBrightcoveExperiences.js https://sslanalyzer.comodoca.com/?url=https%3A%2F%2Fadmin.br...