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

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
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2886
Published: 2014-09-18
GKSu 2.0.2, when sudo-mode is not enabled, uses " (double quote) characters in a gksu-run-helper argument, which allows attackers to execute arbitrary commands in certain situations involving an untrusted substring within this argument, as demonstrated by an untrusted filename encountered during ins...

CVE-2014-4352
Published: 2014-09-18
Address Book in Apple iOS before 8 relies on the hardware UID for its encryption key, which makes it easier for physically proximate attackers to obtain sensitive information by obtaining this UID.

CVE-2014-4353
Published: 2014-09-18
Race condition in iMessage in Apple iOS before 8 allows attackers to obtain sensitive information by leveraging the presence of an attachment after the deletion of its parent (1) iMessage or (2) MMS.

CVE-2014-4354
Published: 2014-09-18
Apple iOS before 8 enables Bluetooth during all upgrade actions, which makes it easier for remote attackers to bypass intended access restrictions via a Bluetooth session.

CVE-2014-4356
Published: 2014-09-18
Apple iOS before 8 does not follow the intended configuration setting for text-message preview on the lock screen, which allows physically proximate attackers to obtain sensitive information by reading this screen.

Best of the Web
Dark Reading Radio