Slashdot Mirror
Google Fixes IE Bug
aussie_a writes "Without accepting blame Google has quickly patched the vulnerability, without requiring users to download a patch. Previously covered by Slashdot, the flaw allowed people to access files and passwords on a computer via any website when viewed with IE while running Google Desktop." From the article: "'Google was able to address the problem quickly because it didn't require changing any code at the user's desktop,' MacDonald said. 'Google applied more stringent security controls on its main site, which shut down the exploit.' The incident does raise important questions about Google as a desktop software vendor and its plans for rolling out future security fixes, said MacDonald. "
Well I'm just glad Google fixed the issue whether it's their fault or not.
//not that I use IE but you know still.
I don't care who's fault it is. Just fix the problem.
-Teiresias
As more and more desktop apps serve as an interface to a website, it'll become a lot easier to fix and deploy new functionality. This is a good thing.
Join the Free Software Foundation
The incident does raise important questions about Google as a desktop software vendor and its plans for rolling out future security fixes, said MacDonald.
I question Mr. MacDonald's credibility. If this is the same gentleman I'm thinking of, he's an older man who has a farm...or at least had one.
The title sounds as if Google had fixed a bug in Internet Explorer's code. Shouldn't it be "Google fixes Google Desktop bug"?
Granted, it does make it sound less like news... but I suppose it's because it isn't, really. You don't see stories like "Adobe fixes Photoshop bug", "KDE team fixes Konqueror bug", etc... since of course that's just part of the daily life in development.
The filesystem is the package manager
Well, I guess.. like "why would you go with Microsoft who sit on a vulnerability for months, instead of someone who actually fixes security holes?"
Its my understanding that this flaw has nothing to do with Google Desktop per se -- but rather was just discovered on Google. Although I'm glad they shut down the flaw where Google is concerned, it seems that it still exists for other programs -- since the security breach itself is not specific to Google.
They fixed their code so that their Desktop Search program couldn't be used maliciously because of a flaw in IE.
"The bug was Google's... ...so why is it headlined "IE Bug"? It's not a bug in IE..."
Actually, the bug IS originally in the IE code. But Google's Desktop implementation of that code failed to address the security hole. In other words: Microsoft created the security hole and Google Desktop made it dangerous. Who's to blame? MS? Google? Both? None? You decide.
SIG: TAKE OFF EVERY 'CAPTAIN'!!
Generally, bash is superior to python in those environments where python is not installed.
First of all, Google did not fix an IE bug. All they did is make their own software a bit more tight in security, so that *they* are not suceptible to the IE bug. It does not *fix* it.
Second of all, the bug was *not* in Google Desktop, it *is* an IE bug, it just happens that people who use Google Desktop are vulnerable to it since it embeds IE.
But *ANY* app that embeds IE is (and remains) vulnerable, including many other pieces of software. For example, for all you poker players, if you have an account a UltimateBet, you *are* vulnerable to ths bug, and in theory someone could use it to steal your account information, which is very dangerous, since they may be able th initate withdraws from your account as well.
This is just the tip of the iceburgm there are literally hundreds of apps that embed the IE engine for rendering. All are at risk.
I think the problem was that the google's software was being run in the "Local Zone", which is almost always highly trusted. The flaw was that a site on the Internet could manipulate the toolbar. Sort of like an XSS vulnerability.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
From the article: "Even though Internet Explorer is the root cause of the vulnerability, Google's changing its Desktop Search so that it was no longer remotely accessible though the vulnerability in IE was the responsible thing for Google to do," said Gartner Research vice president Neil MacDonald.
Need an ISP in South Africa?
Who's to blame? MS? Google? Both? None? You decide.
George W. Bush, clearly.
The bug was an IE bug. Lets say there is a windows exploit out there and it has the potential to let people run arbitrary code on the victim's computer. If that code accesses e-mail files stored on the computer that have usernames / passwords / credit card information....it is not the fault of Thunderbird, Eudora, Netscape, or whatever e-mail client is running there. That isn't how they got in, they got in through the windows exploit. I'm sure google didn't fix the IE bug, they prevented people using that exploit from getting personal information from Google Desktop Search. The IE bug is still there. This will just put less pressure on Microsoft to fix their POS browser.
If I recall previous discussions correctly, the flaw was in MSIE. If that's the case, what's to prevent an attacker from exploiting the flaw with his own code?
If I remember correctly, he was far more concerned with EI than IE.
From CIO Today: The incident does raise important questions about Google as a desktop software vendor and its plans for rolling out future security fixes, said MacDonald.
"Since Google is providing end-user software, it must be held to the same standards that you would hold other desktop software vendors to," he said.
Standards? What standards would those be? Last I checked, most software manufacturers are sending out buggy copies of their code hoping you won't notice, patching it up continuously, then going ahead and doing it repeatedly. And let's not forget that Microsoft is the king of them all!
And exactly how are we to hold them to these "standards"? So many people use Microsoft routinely that they have the lion's share of the market, and their competitors are left with the spoils. And while you may not like MS, many of their programs work just well enough that you believe you've got a decent, everday product. Of course they break down, and people scream and rant, but in the end what do they do? Do they immediately switch to something else? No! They patch up their flawed software and keep the status quo.
It's a classic case of addiction, a lot like gambling but in reverse. You use the software every day and most days it works. The one time it doesn't, you fret, but because you restart it or patch it and it works, you go right back to it, rather than exploring alternatives. And Microsoft counts on this. That's why they dominate - they have everybody "addicted" to their software.
GetOuttaMySpace - The Anti-Social Network
...Shouldn't it be "Google fixes Google Desktop bug"?...
Nope. Object-orientated programming. If the api documentation says that something should operate in a certain way and it does not then by fixing the problem on your side of things it weakens encapsulation of the function and makes it easier for future bugs to accumulate as the totality of code slowly turns to spaghetti.
Shh.
Dick drives Jane's car.
Jane's car has a faulty parking brake.
Dick parks, engages the brake, but the car rolls away.
Dick stops parking on hills.
Important Points
Jane did not fix the parking brake
Dick did not fix the parking brake, but he no longer uses it.
Other drivers may or may not be aware of the broken parking brake.
The potential is still there for the car to roll away.
Yes, a large part of Google Desktop will run in any browser.
But parts of the Sidebar component are rendered using an IE rendering engine. It is simple to verify if you check the references in the EXE and DLLs.
Google didn't fix the IE bug. The IE bug still exists. Only Microsoft can fix the IE bug. What Google did was put in a work around so that exploiting the IE bug won't cause a security risk in Google Desktop.
The IE bug can still affect other software.
Uhmm, not quite. We blame the one who did not do as they should have done. The reason we do not blame the compiler for a buffer overflow is the fact that the overflow resulted because the compiler acted the way it is supposed to. Instead, we blame the programmer who was not aware of this. So far, you're right.
What would you to if your program used libfoo, and libfoo turns out to have a security vulnerability in one of the functions you use? You either update to a new version of libfoo, or you try to restructure your code to avoid using the problematic function.
In this case, it would seem that Google made use of IE as it was supposed to (by API specification), but IE was not secure as it should have been, so Google decided to do it a different way. I do not see how the fault lies with Google, nor why they deserve particular praise. They found out that one of their underlying programs had a security vulnerability with no known fix, so they used a workaround to secure their application.
Microsoft on the other hand just gets a "stupid!" from me for allowing something so easily fixed to blow up in their faces like this. Way too much bad press for such a little thing.
I'd like to clear up some of the confusion the mainstream media has caused.
The bug I found is in Microsoft Internet Explorer and not in Google Desktop. This bug remains in the browser and it is in no way fixed. This bug by itself is a pretty serious one and allows for exploitation of many sites that are not Google related.
My proof of concept code exploited Google Desktop to retrieve private information from a local machine. In order to do that I used the IE bug twice. First I used it on one of Google's sites in order to get a valid key so I can access the local web server that is Google Desktop's interface. The second time was to execute a query on the GDS server and retrieve the results.
Google basically found a quick hack that nullifies the first portion of the exploit, getting the valid key. They added the following piece of HTML code to their sites, right before the "Desktop" link is revealed: "<!--"/*"/*-->". This makes the IE CSS parser think the rest of the page is a comment so the link won't be visible while trying to read the CSS text.
The bug in IE remains at large. And GDS itself is still exploitable. If somebody found an XSS hole in one of Google's sites, he would be able to retrive the GDS key and then use the second portion of the exploit to retrieve local results.
As I said in my original article, this is a serious bug and there's no simple solution for it, at least until IE is fixed.
Matan
Google Desktop apparently uses some CSS style sheets served by their site. The IE vulnerability was in its CSS logic and thus adjusting the CSS on their server avoids the exploit from the Google Desktop vector.
--
Q