29 June 2011 | 12,081 views

Groupon India Subsidiary Leaks 300,000 Plain Text User Passwords

Check For Vulnerabilities with Acunetix

Oh look! Another data-leak, this was was pretty bad as it contained plain-text passwords (who on earth doesn’t hash their passwords in the DB in 2011?!).

Anyway this time it was a Groupon subsidary – Sosata.com which managed to leak the e-mail addresses and plain-text passwords for 300,000 users AND on top of that, Google managed to index it.

The original story was published here:

Groupon leaks entire Indian user database

The leak was discovered by Australian security consultant Daniel Grzelak.

Groupon subsidiary Sosasta.com accidentally published a database containing the email addresses and clear-text passwords of 300,000 users and the cache was indexed by Google.

The trove of personal data was discovered by Australian security consultant Daniel Grzelak as he plugged a handful of query terms into the search engine, he said Tuesday. He contacted Patrick Gray with security blog Risky Biz, which reported that the SQL database contained the details for 300,000 Sosasta account holders.

A Groupon spokesman confirmed that the digital coupon distributor “was alerted to a security issue” on Thursday night and corrected the problem immediately. The issue was limited to Sosasta, which uses its own servers and network and isn’t connected to Groupon’s systems in other countries.

“We have begun notifying our subscribers and advising them to change their Sosasta passwords as soon as possible,” the spokesman said in a statement. “We will keep our Indian subscribers fully informed as we learn more.”

At least this time it seems like someone messed up rather than a hack by LulzSec or Anonymous. And it’s good to see an organization react quickly and responsibly to such an information disclosure, this is sadly a rather rare attribute.

The issue was limited to Sosata and did not effect any Groupon sites in other countries. Sosata users have been notified to change their passwords in the system, and I hope for their sakes not too much password re-use is going on.

I still don’t see the fact that the passwords were un-hashed being addressed anywhere though, doesn’t that concern anyone other than me?

At time of writing, there was no advisory on either the Groupon or Sosasta websites, although Sosasta’s Facebook page contained a notice that came in the form of a JPG image that couldn’t easily be indexed by Google or other search engines. Ah the irony.

According to Risky Biz, Grzelak found the massive cache as he was looking for additions to shouldichangemypassword.com, a side project that indexes email addresses included in more than a dozen high-profile privacy breaches carried out by LulzSec and other hacking groups. The query that hit pay dirt included the terms “filetype:sql” “password” and “gmail.”

“I started scrolling, and scrolling and I couldn’t get to the bottom of the file,” Grzelak told Risky Biz. “Then I realised how big it actually was.”

The Groupon statement didn’t say why passwords weren’t encrypted or why such a sensitive file was publicly available.

The snafu is the latest to expose the folly of using the same password on more than one site, a practice still followed by a shockingly high number of people. If you’re one of them, you ought to consider using a password-management program such as Password Safe or KeePass.

For developers – http auth/password protected directories are good! Hashing passwords is good! Leaking sensitive info is BAD!

Sincerely I doubt anyone reading this site re-uses simplistic passwords for their online accounts – but just in case you do – or know anyone that does – I do recommend using Password Safe or KeePass anyway, keep that shizzle secure yo!

Anyway, I wonder if anyone is going to sue over this?

Source: The Register



Recent in Legal Issues:
- Navy Sys Admin Hacks Into Databases From Aircraft Carrier
- Teen Accused Of Hacking School To Change Grades
- Royal Canadian Mounted Police Arrest Heartbleed Hacker

Related Posts:
- Passera – Generate A Unique Strong Password For Every Website
- Cupid Media Hack Exposes 42 Million Passwords In Plain Text
- FireMaster 2.1 – A Firefox Master Password Recovery Tool

Most Read in Legal Issues:
- Class President Hacks School Grades - 80,538 views
- Hospital Hacker GhostExodus Owns Himself – Arrested - 47,445 views
- One Of The World’s Most Prolific Music Piracy Groups Busted - 43,464 views

Low-cost VPS Hosting

5 Responses to “Groupon India Subsidiary Leaks 300,000 Plain Text User Passwords”

  1. vikram 29 June 2011 at 12:29 pm Permalink

    amazing….. in today’s world … storing plain text password…..

    you is the IT company behind them… they should be executed (like they do in china)…. no mercy….

    i thought IT stands for Indian Talent but this is shameful.

  2. Wojtek 29 June 2011 at 7:48 pm Permalink

    As you mentionned KeePass and Password Safe, another great product to consider is Lastpass.com.
    I do not have any relationshipwith them, just a very happy user.

  3. johnp_80 30 June 2011 at 5:28 am Permalink

    Plain Text? seriously?
    Another good option is KeepassX, its been cross platform supporting a lot longer than Keepass, and doesn’t paint a bullseye on itself like LasPass

  4. Bogwitch 30 June 2011 at 10:24 am Permalink

    “Hashing passwords is good!”

    Hashing passwords is better than leaving them in plaintext, for sure but a simple hashing is not sufficient. We have seen recent hacks, Bitcoin for example, that had hashed passwords but the passwords were easily cracked.
    If you are going to store passwords in a database, and if you’re running a site where users are going to log on you’ll probably have to, you need to run a hashing algorithm multiple times to slow down an adversaries attempt to extract the passwords from the hashes. My most recent site has the hash algorithm run for over 1,000, less than 10,000 times. Sure, there’s additional load on the server but far better than the exposure of account passwords IMO.

    • Darknet 1 July 2011 at 5:53 am Permalink

      Yah I agree, but mostly it’s like this – just make the passwords hard enough to crack so that after a compromise you can everyone to change their passwords in the time before they get cracked. Multiple hashing sure does help (especially if you mix algorithms), and will really slow down extraction. Best of all, don’t let anyone get hold of the hashes in the first place..