Websites Can Detect What Chrome Extensions You've Installed
dsinc writes "A Polish security researcher, Krzysztof Kotowicz, makes an worrisome entry in his blog: with a few lines of Javascript,
any web site could list the extensions installed in Chrome (and the other browsers of the Chromium family). Proof of concept is provided here. As there are addons which deal with very personal things like pregnancy or religion, the easiness of access to those very private elements of your life is really troubling." Note: the proof of concept works, so don't click that link if the concept bothers you.
Yet another way that IE is better than Chrome.
The proof-of-concept listed only four out of my ten enabled extensions. Among those left out were Google Calendar, UA Spoofer, and Pastebin, among others. I'd say this 'exploit', if we can call it that, has a long way to go...
Hyperbole: I use it liberally!
This can be used in a much more mundane way - a website can check if you have Adblock installed, and it can refuse to display its content to you then unless you uninstall it.
Wow. Browser sniffing. What year is it?
If you want news from today, you have to come back tomorrow.
Doesn't list anything, even if I enable Javascript for its site in NotScripts (yet another reason to install this little lifesaver).
Erm...how is that related in the slightest?
If they wanted this to happen, it would have been made an awful lot easier to do.
So let me get this straight - I can click on that link right now in Firefox and it's going to tell me what Chrome extensions I have installed? Unbelievable!
#DeleteChrome
...and I use Chromium, but I don't have any extensions :>
(yes yes i realise that's beside the point ;p)
Guess someone should really post this on the SRWare Iron's forums/mailing list (and other privacy-centered Chromium based browers) so they can disable the functionality in their builds...
This "exploit" looks more like begging the question to me. As far as I can remember, every single Chrome extension I have installed warned me that it might share data with the websites I visit before I installed it. It stands to reason that if an extension can share data with a website, that website can detect the extension, does it not?
I'm not saying that it's ideal behavior, only that it seems to me that Chrome users have already been warned about it by Google itself. If you don't like the behavior, you have quite a few options: Remove the extension, disable it, go incognito when you don't want your extensions detected, or simply use another browser come immediately to mind.
Disclaimer: the original (and only) NoScript can be detected as well, but at least you couldn't be notified by a JavaScript alert() box on a page where JavaScript isn't supposed to run ;)
There's a browser safer than Firefox, it is Firefox, with NoScript
And don't get me started on that useless enterprise-y software which thinks it needs to be "browser based".
For example: We now run multiple client based software packages for different tasks in our company. They can be configured to interact any way we choose. (for example a document from content management can be opened INSIDE the point of sale software, so that people at the cash register can view documents pertaining to the customer currently in transaction, so that they can for example pull up the letter the customer claimed to have sent last week to your central office.
When about a decade ago "web based" solution started to happen at first we thought "oh, cool, stuff like that will get easier because sooner or later all calls like that can be done via HTTP and URLs. In our own client applications we now use HTTP a lot to request data from other systems in the background. Protocol wise it's a really nice thing.
But putting the *FRONTEND* of an enterprise application into the browser is pretty messed up, since most of the time you need a lot of integration between different system on the user side, and that is pretty much forbidden by the browser security model.
What I think is *really* needed for HTML5 Enterprise "GUIs" to work is a separate HTML/CSS/JavaScript display application for "trusted apps" that can interact freely with everything and a "web browser" for the public Internet. Or some way to tell a browser that THIS signed "application" is allowed to talk to THAT signed "application" even with cross-site scripting.
A lot of extensions request access to your browser's X, Y, & Z... and sometimes your entire file system (???) But since we (the user/s) wants to use the provided functionality in the extension, we all click "OK". Just from reading those notifications, it is still unclear WHY the extension needs those access permissions, or WHAT the extension might be doing with said access. How can we know/understand more about this process? Where is the source path of the extension & should we just be looking at the source code (assuming dev experience)?
/. has at least one article, last year I think, that mentioned this fact already.
This is not a secret and a moderately well known fact.
Troll is not a replacement for I disagree.
People who use typically choose Chrome (the Google Browser) don't strike me as people who are all THAT concerned about their privacy. It might be a nice browser, but it is closed-source, and heavy into the "Google way" (which to me means to share all your information with Google).
At least with Chromium, people can see what is going on inside...
And that's why they already updated the plugin system to avoid this exploit, then, is it?
I think somebody jumped the gun here, 'cause I'm using Chrome 17.0.963.79 on Ubuntu 11.10, and that "proof of concept" link didn't list any of my extensions.
It only detected half of the plugins I have installed.....
Yes sure, Since it was searching by ID I can understand why it did not get some of my extensions (unusual ones like gpgAuth) , but it also said I was using Website Blocker (Beta), which I am not.
Since that's my first and foremost extension for everything at all times.
Which probably means that one of your extensions has an ID collision with Website Blocker (Beta). It would be interesting to find out which one it is.
The proof of concept proves that you are okay if you have disabled JavaScript by default.
huh!
:)
Last 3 months I developed my tiny web-coding sandboxie, and it was my first work:
http://www.browserleaks.com/chrome
Same idea, but it more visual demo, cos it uses apps icons detection.
By some reason I didn't try to use manifest, and write huge parser to collect 10k db...