Linked by Thom Holwerda on Fri 20th Nov 2009 16:53 UTC
Mozilla & Gecko clones One of the main reasons why Firefox has become so successful is its extension framework, and the large community of extensions developers that has grown around it. What many users are not aware of, however, is that extensions are a bit of a security nightmare.
Order by: Score:
This stands to reason
by libray on Fri 20th Nov 2009 17:47 UTC
libray
Member since:
2005-08-27

Any third party extension, just like a third party application, does not have to go through the same code review or testing that may or may not happen by the vendor.

From the article, there is at least one vulnerability against an arbitrary extension to attack the noscript extension's whitelist. Malware writers are aware of the safeguards that users install and thus are making inroads to the weaker links in our chains of armor.

You hear often that what gives Firefox the edge over other browsers are the extension, and so this is the biggest hurdle security-wise. The same can almost be said for Windows especially in the business world.

Reply Score: 2

jabbotts Member since:
2007-09-06

Heck, not just browsers or OS (viewing third party software as plugins of sorts). I hear Facebook's API is actually very good but the wild west of third party applets blows it all to hell. It seems any plugin framework's time for a security review is coming due.

Reply Score: 2

ChromeOS
by henno on Fri 20th Nov 2009 19:15 UTC
henno
Member since:
2009-06-25

The recent video on ChromeOS security

http://www.youtube.com/watch?v=A9WVmNfgjtQ&feature=player_embedded

takes the sandboxing quite seriously. Maybe the Mozilla developers could have a look at the Chrome security model (which works even better on a device that has ChromeOS, due to trusted booting, etc.), which I'm sure they are....

Reply Score: 1

RE: ChromeOS
by unwiredben on Fri 20th Nov 2009 19:56 UTC in reply to "ChromeOS"
unwiredben Member since:
2009-07-10

One of the current projects at Mozilla is called Electrolysis, and it's working at moving page rendering and plugins into separate processes so they can operate separately from the browser UI, effectively giving the browser the same security profile as Chrome. I think we're aiming for FF 3.7 for this, but it might be 4.0 since moving things to separate processes will break a lot of the methods extensions use to interact with the browser.

Reply Score: 2

RE: ChromeOS
by flanque on Sat 21st Nov 2009 02:53 UTC in reply to "ChromeOS"
flanque Member since:
2005-12-15

I'd expect sandboxing to become increasingly necessary and popular.

Reply Score: 2

Typos
by drstorm on Fri 20th Nov 2009 21:15 UTC
drstorm
Member since:
2009-04-24

Maybe some attention to the security problems in the extension framework pushes Mozilal do think about some way to change this framework to solve or mitigate the issue.

Reply Score: 2

Yoono Fixed
by tpringle on Tue 24th Nov 2009 01:47 UTC
tpringle
Member since:
2009-11-24

The Yoono vulnerability in this article was fixed in Yoono 6.2 which was released in August. You can download it at http://www.yoono.com

Reply Score: 1