Perimeter
12/13/2010
04:33 PM
Commentary
Commentary
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

What The Gawker Compromise Really Reveals

Passwords are only half of the defense against compromise --unfortunately, the other half is being crippled by the login policies of many online providers.

This past weekend the Gawker Media servers were compromised and 1.3 million login credentials were stolen. While the passwords were encrypted, the method used wasn't the strongest. The end result? At least one-third of the passwords have already been cracked, and some believe that another third can feasibly be cracked as well.

Much of the advice circulating around the Gawker attack has revolved around changing your Gawker Media account passwords. And this includes not only Gawker.com, but also Lifehacker, Gizmodo, Jezebel, io9, Jalopnik, Kotaku, Deadspin, and Fleshbot, as well.

However, that advice ignores the real problem: the fact that these sites require your email address be used as your username.

Sure, you could set up bogus email accounts for each online account you use, but that's a pretty cumbersome workaround. So in very, very many cases you will find that the username is identical to one used on other sites. And that's really the crux of the problem.

Twitter wasn't involved in the compromise. However, because Twitter also requires an email account to login, the attackers don't need the Twitter username to break into those accounts. If they know someone@email.com has password123 on Gawker, then they can use that same someone@email.com to see if they have a Twitter account. And if they do, they can then try the same password.

The username should serve as half the account security. Instead, forced practices by many online providers cripple that half and leave the password as the only barrier to entry. In my opinion, this is the real weakness the Gawker Media compromise reveals.

Mary Landesman is an antivirus professional and senior security researcher for ScanSafe, now part of Cisco. In 2009 she was awarded a Microsoft MVP for her work in consumer security.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web