Slashdot Mirror


Gmail Accounts Vulnerable to XSS Exploit

mallumax writes "A security hole in GMail has been found (an XSS vulnerability) which allows access to user accounts without authentication. What makes the exploit worse is the fact that changing passwords doesn't help. The full details of the exploit haven't been disclosed. The vulnerability was reported by Israeli news site Nana. They were tipped off by an Israeli hacker. Google has been notified and they are working to close the hole. The Register has the story here."

25 of 232 comments (clear)

  1. Isn't it... by Sheetrock · · Score: 2, Insightful

    just a bit irresponsible to be coming out with this before Google has had a chance to fix it?

    --

    Try not. Do or do not, there is no try.
    -- Dr. Spock, stardate 2822-3.




    1. Re:Isn't it... by realdpk · · Score: 4, Insightful

      No. Certainly not. People should be made aware of security issues. Especially for free services like this, where people have no guarantee they will ever be addressed.

    2. Re:Isn't it... by LiquidCoooled · · Score: 4, Insightful

      Its not like a local exploit where we can stop using it, or update ourselves.

      This SHOULD get maximum exposure. Maybe then the heads in google will jump on this with all their PHDs.

      As for not fixing it, I doubt thats an option. Such a monumental failure so start in their public offering will be devistating to them.

      --
      liqbase :: faster than paper
    3. Re:Isn't it... by lukewarmfusion · · Score: 4, Insightful

      Yes and no.

      Yes - Google should have the opportunity to fix this appropriately, not racing against the slew of hackers, crackers, and script kiddies that want to exploit it.

      No - People should aware of security risks in the software, hardware, etc. that they use and upon which they rely.

      Personally, I prefer to inform the company of vulnerabilities and offer to help fix them. It's helped me land clients and discredit competitors.

    4. Re:Isn't it... by LiquidCoooled · · Score: 2, Insightful

      I should clarify that apart from deleting all my mail and closing my account I can do nothing about it. I don't want to lose my account though, I *like* gmail, and certainly don't want to go back to the hotmail wasteground.

      (and also look sheepishly at the grammatical screwup in my previous post)

      --
      liqbase :: faster than paper
    5. Re:Isn't it... by Saratoga+C++ · · Score: 2, Insightful

      To be honest I think google's getting off easy.

      Just about every MS security hole that comes out has the exploit code attached. Sense google's not an "evil" company the exploit is kept secret? What is the reason that an Operating System Security Hole is given with code and a beta webmail service exploit isn't?
      IIRC: Wasn't hotmail's exploit also given with a snippit of code/instructions on how to do it? This is the same thing but with a different company.

      I'm not trying to say "release the 'sploit" but I am saying that it does set a set of different standards for companies that offer the same service (e-mail over a web based interface). Why is it that one is realeased (and linked on slashdot iirc) and one is kept from prying eyes (Keep gmail safe)?

    6. Re:Isn't it... by Saratoga+C++ · · Score: 2, Insightful

      Yes, yes it is and I"ll tell you why.

      In both instances your harmnig the user with these exploites (given hotmail/gmail's exploits). Also with the OS exploites. The users is harmed. Sure this indirectly harms MS but your still exposing the users of the product.

      What this amounts to IMHO is that for some reason gmail users are more precious then hotmail users or that hotmail users diserve to be hacked becuause they are users of the service. Thats shows a rather large power trip issue on the part of the person reporting the exploit.

  2. Re:XSS isn't that big a deal by Sheetrock · · Score: 4, Insightful
    Well, the problem is that we're looking at each individual XSS exploit as a vulnerability when we should be looking at XSS itself as an unwholesome feature in general.

    Like when we started treating e-mail as a file transfer protocol, or when documents began to contain executable content, XSS gives an avenue of attack by adding a new and unrequested behavior to something that used to be secure. We need to reduce these channels of exploitation if computers are going to become secure -- especially as we head towards a homogenized environment on the Internet with regards to executable code (.NET/Java).

    --

    Try not. Do or do not, there is no try.
    -- Dr. Spock, stardate 2822-3.




  3. Re:it IS a beta... by buzzini · · Score: 5, Insightful

    Labeling something "beta" almost indefinitely should not be a get-out-of-jail-free card. It seems to me that once a product is in fairly widespread use -- once a product has a marketing plan behind it -- saying "no fair, it's a beta!" is a little disingenuous.

  4. Easy Fix: by thesandtiger · · Score: 5, Insightful

    1) Gmail plugs the hole.

    2) They change the cookie validation test script in this case to require a different cookie than ones that were being given while the exploit was active.

    3) When a counterfeit cookie (or any of the old cookies) tries to validate it's immediately seen as invalid, and the user is then made to login.

    Of course, if someone already got at your stuff, well, that's bad.

    --
    Since I can't tell them apart, I treat all ACs as the same person.
  5. Re:Good thing they are still in beta. by Anonymous Coward · · Score: 1, Insightful

    They can call it beta all they want, but they obviously want people to use it as their primary e-mail account now. Just because they call it beta, doesn't exempt them from responsibility when they put their product out on the open market.

  6. Not a real problem. by NotoriousQ · · Score: 4, Insightful

    No worries! Remember it is still a beta. It is not like anyone will use this for a serious purpose.

    --
    badness 10000
    1. Re:Not a real problem. by verbatim_verbose · · Score: 2, Insightful

      Parent should have probably been marked funny rather than insightful... sheesh.

      The thousands of people using Gmail don't care that it has a little tiny word "beta" at the top. They've got mail in there that probably shouldn't be seen by other people. (Personal communications, private chats, possibly much more.)

      It IS a real problem for anyone who doesn't want their email being read by others.

  7. Re:Wives by Anonymous Coward · · Score: 1, Insightful
    It's easier to tell than that. For instance: is she spending the week-end with a "friend"? Leaving Friday night and coming home late Sunday "too tired" to do anything? Is this occurring every week-end?

    Does she go out drinking with this same "friend" 2-3 times per night? Every week? Often drinking at fetish clubs or going to swinging events, again with this same "friend"?

    Those are much easier signs to look for than snooping through e-mail :-)

  8. overstatement of exposure by elmegil · · Score: 2, Insightful
    "Because Gmail offers a gigabyte of storage, several times bigger than most other web based mail services, users hardly delete any old correspondence", says Goldshlagger. "The result is a huge amount of mail accumulating in the users' boxes, which frequently include bank notices, passwords, private documents and other files the user wanted to backup. Who ever takes a hold of this data, could literally take over the victim's life and identity".

    If you've got ALL THAT INFORMATION already migrated to a BETA service that's been around for ... a handful of months, you're pretty foolish. As far as it goes, I specifically DON'T have anything particularly importang going to my gmail account for exactly this reason--it's unproven as of yet. In fact, I had a two week outage, totally unable to use my gmail box, for uknown reasons. After working with the GMail team, it got fixed, but they never told me the actual cause. Yet another reason not to trust BETA software/services with really crucial information.

    And before all the 'bots claim I'm bashing google, quite the contrary. I love GMail. But it's like any other BETA product right now--still working out the kinks.

    --
    7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
  9. Re:Now everybody,not just Google,can read your ema by VidEdit · · Score: 2, Insightful

    Troll? While I didn't necisarily think the parent post would be moded up, I certainly don't think it deserved a -1! Sigh, out of my hands...I certainly didn't mean to be a troll. I do think that it is legitimate to point out that email is plaintext and that GMail accounts are, in certain ways, already compromised. Seems people are very protective about their GMail...

    --
  10. Re:Hmmm.... by Anonymous Coward · · Score: 2, Insightful

    Free Flat Screen HERE!

    Please put your fucking "free stuff" spam in your sig, so those of us who turn sig display off to avoid having to read "free stuff" spam don't have to read it. Thank you.

  11. Re:it IS a beta... by pipingguy · · Score: 2, Insightful


    Labeling something "beta" almost indefinitely should not be a get-out-of-jail-free card. It seems to me that once a product is in fairly widespread use -- once a product has a marketing plan behind it -- saying "no fair, it's a beta!" is a little disingenuous.

    Agreed, maybe Google is laurel resting in the wake of the IPO.

    Do you remember web searching prior-Google? I used to take pride in knowing the Hotbot and AltaVista switches (and nand not) but Google's 1998 blew all that away. That level of knowledge was no longer necessary. There's probably a lesson in there somewhere.

  12. Re:XSS isn't that big a deal by mallumax · · Score: 2, Insightful

    XSS was highlighted because that's easiest way to steal the cookie without physical access to the machine which the victim uses.(correct me if i'm wrong).XSS makes it extremely easy for an attcker to social engineer a user into divulging his cookie, using a malformed hyper link in a mail. Though GMail was initially limited to computer savvy people it has now percolated to the masses.As the spread of recent viruses have shown social engineering normal users is trivial.

  13. Re:MOD PARENT IDIOT by psbrogna · · Score: 2, Insightful
    Starting a session over because a user lost his dialup connection is acceptable to every user I've run into.

    This technique has been in use at several moderate (> 50k users/mo) traffic sites I've worked on with no problems and no complaints for several years. And, state control is completely server side.

    If you like cookies, off you go. I'll choose the more secure solution for now.

  14. Re:Need more than just the username by poot_rootbeer · · Score: 5, Insightful

    you need to actually trick the user into giving you their GMail cookie by phishing. ...or by grabbing the cookies left behind by previous users off a public terminal.

    But that's a minor concern, no one ever uses a public computing terminal to check webmail, or walks away without logging out properly.

  15. Re:it IS a beta... by WIAKywbfatw · · Score: 5, Insightful

    Care to explain what marketing plan for Gmail you've seen? So far, Google has issued a couple of press releases - announcing its intention to offer email services, etc - but nothing more than that, and it's made it repeatedly clear that the service is in beta.

    Have you ever seen more than that? Have you seen any advertising (banner or otherwise) for the service? Just how do you contend that Google is marketing it?

    And how the hell are you defining "fairly widespread use"? Just how many Gmail accounts do you think there are? 100,000? A million? Well, in comparison, how many Microsoft Hotmail or Yahoo Mail accounts do you think there are out there? I'd be surprised if Gmail had even a hundredth of the user base that its key competitors possess.

    Gmail is in beta. Until they say it's not in beta please accept that nothing should be taken for granted. And the fact is that even "shipped" products aren't error free, so either learn to accept that things sometimes go wrong with software or just stop using a PC altogether.

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  16. Re:Google needs to toss its cookies... by rnicey · · Score: 1, Insightful

    It's really iffy design.

    The hash or whatever that validates the cookie's authenticity should have the IP address and expiry time (from the servers point of view) embedded in it. Why this isn't part of some standard library for a software house like Google makes me wonder...

  17. Re:Google needs to toss its cookies... by casuist99 · · Score: 2, Insightful

    My immediate concern is the fskers who live in my apartment complex. We use a shared internet connection (300 of us on a dual T-1, ouch) for the entire complex. Now, I can't be the only person who knows that an un-administered network (no kidding) will be rife with people screwing around.

    I know that my email travels through routers and ISPs in the clear, but they probably don't know me personally. I'm more worried about my roommates sniffing the traffic coming from my computer to the gateway and reading my email. Or the shithead upstairs who I've called the cops on. You get my point.

    Important stuff, duh you've got to be encrypting it from sender-to-receiver. Semi-private stuff, I'd at least like to know my neighbors aren't reading. https://gmail.google.com/gmail is very helpful to me for that purpose. Thanks for pointing that out.

  18. Re:The Microsoft argument by JibberJim · · Score: 3, Insightful

    As the reporter of the first bug reported in the register article, I certainly didn't go looking for it because of google, it was trivial to find, I found it 2 1/2 years ago (you can see a usenet post from 2002 which describes it, when XSS into google didn't matter much, phishing was new, and google had no data)

    The reason we're getting this deluge of security flaws in google now is simply because people are now looking, they're easy to find, the XSS flaws are trivial (like ignoring you're encode user input before writing it into the page)

    The issues are Googles lack of QA and security testing - do you think it's reasonable to release an HTML product which searhed personal data on peoples machines without having a test which provided some javascript as the search term? I think the failure to do that is incompetence of a level that makes MS's old security look good.

    Yes, Google have fixed the flaws quickly, that's because the flaws are trivially easy to fix - html encoding a string isn't hard, even in python.