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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7392
Published: 2014-07-22
Gitlist allows remote attackers to execute arbitrary commands via shell metacharacters in a file name to Source/.

CVE-2014-2385
Published: 2014-07-22
Multiple cross-site scripting (XSS) vulnerabilities in the web UI in Sophos Anti-Virus for Linux before 9.6.1 allow local users to inject arbitrary web script or HTML via the (1) newListList:ExcludeFileOnExpression, (2) newListList:ExcludeFilesystems, or (3) newListList:ExcludeMountPaths parameter t...

CVE-2014-3518
Published: 2014-07-22
jmx-remoting.sar in JBoss Remoting, as used in Red Hat JBoss Enterprise Application Platform (JEAP) 5.2.0, Red Hat JBoss BRMS 5.3.1, Red Hat JBoss Portal Platform 5.2.2, and Red Hat JBoss SOA Platform 5.3.1, does not properly implement the JSR 160 specification, which allows remote attackers to exec...

CVE-2014-3530
Published: 2014-07-22
The org.picketlink.common.util.DocumentUtil.getDocumentBuilderFactory method in PicketLink, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 5.2.0 and 6.2.4, expands entity references, which allows remote attackers to read arbitrary code and possibly have other unspecified impact via...

CVE-2014-4326
Published: 2014-07-22
Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) zabbix.rb or (2) nagios_nsca.rb in outputs/.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.