Skip to the links

Call Me Al

My MozBlog

If you're not aware, some new security holes have been found in Firefox. Ok, so that sort of thing happens from time to time. This is the first one that has seriously bothered me. The reason is that it affects UMO. To put it simply, the bug exploits the XPI whitelist. Well, there's a lot more to it than that, but that's how it affects me. There is only one site on the whitelist: UMO. The only way to prevent this particular situation from being abused is to make UMO not be trusted. The solution: do-not-add.mozilla.org. This means that UMO has suddenly become very annoying. The only permanent solution will be for everyone to upgrade to the very latest version of the browser once a patch is released. I hope that mozilla.org will backport the bug to every affected branch. I also hope that they are able to release the change as a binary patch. Even better would be instructions for people to make their own binary patch if they redistribute or compile the browser themselves.

Of course any site that you've added to your XPI whitelist is vulnerable. That means that UMO will have to permanently filter out the older user agents and force them to upgrade. If you choose to spoof your UA instead of patching, then you're being dumb.

I think that what bothers me the most is that this bug isn't the fault of UMO, but we get punished for it. And there's nothing I can do about it. I feel so powerless.

4 comments - Post a Comment
I think that knowing this UMO should not be whitelisted by default. Before running any update on the Mozilla-software the software should check whether UMO is on the whitelist. I think in the end digitally signing updates would be better than just whitelisting an update-site. Digitally signed updates from Mozilla.org could be trusted (if this cannot be exploited) and extensions from other places could still be whitelisted.
This is the second (maybe the third) incident I'm aware of where a feature put in for the user's convenience ended up revealing a security hole. Bug 259708 had another.
So the one where XPCOM could be called by just loading a page wasn't bad?
Advertising can be a big problem otherwise. A lot of companies reserve a big chunk of their budgets to cover marketing expenditures.
Post a Comment


powered by blogger