Google Chrome Extension Steals Login Details
An anonymous reader sends word of a proof-of-concept Google Chrome browser extension that steals users' login details. The developer, Andreas Grech, says that he is trying to raise awareness about security among end users, and therefore chose Chrome as a test-bed because of its reputation as the safest browser. Grech says he does not doubt that Chrome is a safe browser, but the point is that such an extension could be written for any of them. Grech says he has not uploaded his extension to the Google Chrome repository or anywhere else; but he has published enough details to allow others to reproduce the technique easily.
How is this different than just downloading and installing a program? Chrome (and Firefox for that matter) give you a warning about trusting the source before installing an extension. Does it surprise anyone that allowing malicious code to run on their computer can expose their information?
WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
He's just doing basic stuff here with that extension. When you try to install any extension Chrome throws up a warning that the extension can access your personal data on whatever sites the extension author has requested access to in the manifest.json file. Ignore that warning at your own peril, especially if it doesn't match with what the extension description says it should do.
Lots of extensions inject content scripts. Lots of extensions do random AJAX calls to random sites that the user doesn't have open in a tab. That he put the two together to steal data is hardly revolutionary.
The only problem I see is that if the author specifies enough websites in their extension permissions, Chrome truncates them to "multiple sites" which is a bit ambiguous.
Guy learns to program, abuses trust of software users. Film at 11?
... a proof-of-concept Google Chrome browser extension that steal users' login details.
That's nothing. Wait till you see my research on what's possible when you get the user to install a malicious kernel module ...
Is this different than someone deciding to run a bash script that wipes their hard drive, as root?
So you can install an extension that's bad. Like you can open an e-mail attachment that's bad. Like you can open a programmable document that has a bad macro.
Seriously, where's the security concern? Don't install crap extensions and you won't have your passwords stolen through crap extensions. Easy enough?
how about a sandbox? How about stealing some Ideas from java? I think one can introduce a "Wants to read password" exception" or a "wants to transfer data outside" exception. And at least firefox points out to me that installing extensions requires thrusting the author
> For now, only install plugins from people you know and trust...
Um, "for now"?
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
They ARE censoring their search results. And they are doing that everywhere, not just China. What makes you think they aren't? Because they say so? Please... stop
For justice, we must go to Don Corleone
So, he created a plugin that let him do what the plugin architecture is designed to allow him to do? I'm not sure how this is newsworthy...
[citation needed]
I really hate to do this but unless you can back that up, then please...stop
*sigh*
For justice, we must go to Don Corleone
capable of running whatever code I instruct it to? Waah, I want big government/big business to protect me!
Seriously though, this isn't news. Extensions are intended to be general purpose, and in order to be powerful enough to do what you want, some risks are taken. I suppose you could take a partial sandboxing approach such as BitFrost or that taken in Android to warn users of what permissions are being requested (and mitigate the effect of expoits), but there's a tradeoff between functionality and safety.
93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
USA! USA! USA! USA!
Uh, wait a minute.
RIP America
July 4, 1776 - September 11, 2001
Security is only as effective as the experience and intelligence and of the user. You can't fix stupid. - Ron White
I wrote an extension to FF long ago that was reading any form field at all, including password fields and was able to send this information to any address on the web via an http call. Starting from FF version 2 the method I used to read the form field (basically enumerating the form input fields with javascript) could no longer read the password field from a form.
You can't handle the truth.
Troll??? HAHAHAHA!
Fanbois to the rescue...
For justice, we must go to Don Corleone
Executing arbitrary code downloaded from the internet might lead to arbitrary code execution. Not news.
WTF am I doing replying to an AC at 5 A.M on a Friday night?
I was under the impression we were talking about Google Chrome and how an add-on has the capability of capturing user data / ids and passwords!
your original post claimed that these types of security holes were inevitable, the only way to combat them is with informed and careful users.
I countered that another way to counter them (even with uninformed and un-careful users) is to place all your users in a padded room which locks from the outside.
Someone should illustrate his lack of body armor by shooting at him with a large caliber rifle.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
The reasons make no difference. They are censoring.. Oh, and fuck copyright! Its sole reason for existence is censorship.
For justice, we must go to Don Corleone
"Evidence exists that browser plugins and extensions are providing a lot of leaks and possibilities for intrusions."
*coughFLASHcoughJAVASCRIPTcoughACTIVEXcough*
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
I don't know of any browser that can't disable JS. With NoScript you can even do it on a per domain basis.
Dilbert RSS feed
...WHY Google allows so much potential access of personal data to installed Extensions?!
I mean every time I tried to install an extension on Chrome I got the warning that it could potentially access my user data and or browser history, and I still don't see any reason that extensions should (even potentially) be allowed access to that information!
I'm honest enough to admit I lie to myself.
controversial hate speech laws = censorship
copyright = censorship
And in direct violation of the 1st Amendment
You are wrong.
In this case it is.
For justice, we must go to Don Corleone
You cannot acquire any rights through censorship. Any and all regulation of speech is censorship.
For justice, we must go to Don Corleone
to some malicious extension or application available for the iPhone. My whole point is that it is possible to protect against clueless users installing a malicious app if you have a closed centrally managed app store. The GP post claimed that the only protection was user education.
Oh, and Chrome is built on top of WebKit also, genius.
It's not about memorizing facts, or about recalling something, it's about knowing what you know and what you don't know. I don't know how to use a chainsaw properly, but I know enough to know that I don't know, and that I would need to learn how or I'm going to get hurt.
If it is easier to simply design in a safety than to educate everyone and keep them educated, then building in the safety is the proper thing to do.
That's true, if the safety has no downsides whatsoever. Otherwise, it bears more discussion.
For example, the iPhone and the Great Firewall of China, both of which claim to be making things more secure and stable for you by removing your choice. Even if the iPhone is more secure for the kind of user who would download BonziBuddy, I don't think it's worth it, and this is exactly what is meant by dumbing down. Compare that to your idea:
I still don't understand why current operating systems don't indicate the priviledge level an application is running at by, say, a coloured border. You'd still need to educate people on what it means, but a fairly simple safety gives them a lot more options than the stupid "well, you could open a console and run ps" geek solution.
But for this to work, you need to educate people on a hell of a lot more than "Here's a colored border." You need to educate them on what privilege separation means, why they might trust or not trust a given program, why they should trust things as little as possible, etc.
It requires fundamental education, much like you'd get from driver's education, to be truly useful. Yes, we should include antilock brakes, but those cannot be a substitute for knowing something about hydroplaning and ice.
You don't need to know how to change your oil -- you can pay someone else to do that. You don't even need to know how often to pay someone else to change your oil. You just need to know that cars occasionally need maintenance, and that before buying a car, you should learn what you need to know to maintain it.
To bring it back to the original "fire" example: If there are no disadvantages, we should make it so no one wants to look into their gas tank with a lighter. But there's a limit to how much idiot-proofing you can do. If you don't teach people that fire and gasoline don't mix, or about flammability in general, stupidity will find a way.
Don't thank God, thank a doctor!
Safari on iOS (iPad, iPhone, iPod) doesn't have extensions. On iOS, instead of an extension, the developer just creates a whole other browser, and that has to be audited to be deployed. Although you may be able to write this for Safari on Mac/Windows, those extensions have to be signed to run, and signatures can be revoked immediately, so even if you got this deployed, at the first sign of trouble it stops running on 100% of systems. There is very little point in tagging a wall that can repaint itself instantly.
One problem with modern communication is the tendency to paint with too broad a brush. You found an attack vector in Chrome, that is real work, a scientific result. Don't fuck that up those hours of work by spending 1 second trumpeting an assumption that it works everywhere else. Either do the work to create the same extension on all other browsers or don't even fucking mention any other browser.
Installing another mouse on your computer steals your cursor control.
You might lose your valuables if you let a robber into your Home...
It's not like anyone doubted this could be done. It is pretty obvious that passwords can be stolen by browser extension mechanisms. Why do we need to be giving bad guys a cookbook?
Do we publish proof of concepts of mass murder techniques, money laundering techniques, and drug dealing techniques?
Who and why is it considered ethical to publish instructions for password stealing in the general media?
I am a little confused here. This article very specifically singles out Google Chrome. But, it turns out the same thing could be done with any browser?
Chrome extensions are sandboxed, unlike firefox extensions. Through the extension API there is no access to the password database for extensions. Even when the user looks at passwords in chrome the password is not written in a window, it is written directly on the canvas, giving no access to hackers.
The only way to get to the password database is to connect directly to the opensql database and decrypt the passwords with the userID - and that is how chrome password dumpers work.
this story is pretty meaningless - and has nothing to do with Chrome or really with Browsers.
Though it is an interesting idea to prohibit access to passworded objects in the DOM - but that would prevent "password strength checkers" to work.