Risk
6/8/2011
12:53 PM
50%
50%

Sony Breach Reveals Users Lax With Password Security

Analysis of recent hacks finds that people commonly reuse logins and choose easy-to-crack passwords.

10 Massive Security Breaches
(click image for larger view)
Slideshow: 10 Massive Security Breaches
Who's got the better security, you or Sony?

Based on an analysis of SonyPictures.com users, half of passwords use fewer than eight characters, only 4% of passwords use more than three character types (uppercase, lowercase, numbers), and fewer than 1% of passwords use non-alphanumeric characters. Furthermore, two-thirds of people reuse their passwords on other websites.

Those findings come by way of software architect Troy Hunt, who analyzed the SonyPictures.com user account information recently released by the LulzSec hacking group. Based on that analysis "users continue to apply lousy password practices," he said in a blog post. "Sony's breach is Sony's fault, no doubt, but a whole bunch of people have made the situation far worse than it needs to be through reuse."

Indeed, while 17 different Sony websites may have been hacked in the past two months-- making the company, in the words of one security industry watcher, "a laughing stock amongst the hacking community," most Sony website users don't have anything to laugh at.

How prevalent is password reuse? To find out, Hunt looked at two of the Sony databases released by LulzSec, and found that they contained over 2,000 identical email addresses, meaning that "someone has registered on both databases," he said. But had they used different passwords? In fact, 92% of people used the same password. Perhaps, however, they were just reusing the same password on multiple Sony websites?

To find out, Hunt compared the 37,608 Sony passwords released by LulzSec, to data from last year's hack of Gawker by the Gnosis group, which led to 188,000 Gawker users' credentials being publicly disclosed.

"Although there were only 88 email addresses found in common with Sony (I had thought it might be a bit higher but then again, they're pretty independent fields), the results are still very interesting," said Hunt. Namely, 67% of people with accounts at both Sony and Gawker used the same password in both places. In other words, password reuse continues to be a problem.

Thankfully, people did at least choose relatively unique passwords. "There weren't a whole lot of instances of multiple people choosing the same password," said Hunt. In addition, the top 25 passwords seen--including "seinfeld," "password," and "123456"--only accounted for 2.5% of all passwords, while "80% of passwords actually only occurred once." Some choices, however, are better than others. For example, 36% of passwords that people chose are simply a word that appears in the dictionary, meaning that it would be easily susceptible to a dictionary attack.

Poor password practices, and people selecting relatively simple and thus easy-to-crack passwords, are nothing new. But security researchers say another significant problem is that too many websites don't properly enforce strong passwords, or properly secure stored passwords. As a result, thanks to rampant reuse of passwords, an attacker can compromise a poorly secured website, harvest user credentials, then use them to access more secure websites.

Of course, then there's Sony, which simply failed to encrypt passwords stored on a publicly accessible Web server, for example by using a cryptographic hash function such as MD5. "Sony has clearly screwed up big time here, no doubt," said Hunt. "The usual process with these exploits is to berate the responsible organization for only using MD5 or because they didn't salt the password before hashing, but to not even attempt to obfuscate passwords and simply store them in the clear? Wow."

In this special retrospective of recent news coverage, Dark Reading offers a look at the lessons learned from the most common database security mistakes and big-time breaches, as well as tips for how to avoid them. Download it now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-5395
Published: 2014-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3276 and E3236 TCPU before V200R002B470D13SP00C00 and WebUI before V100R007B100D03SP01C03, E5180s-22 before 21.270.21.00.00, and E586Bs-2 before 21.322.10.00.889 allow remote attackers to hijack the authentication of users ...

CVE-2014-7137
Published: 2014-11-21
Multiple SQL injection vulnerabilities in Dolibarr ERP/CRM before 3.6.1 allow remote authenticated users to execute arbitrary SQL commands via the (1) contactid parameter in an addcontact action, (2) ligne parameter in a swapstatut action, or (3) project_ref parameter to projet/tasks/contact.php; (4...

CVE-2014-7871
Published: 2014-11-21
SQL injection vulnerability in Open-Xchange (OX) AppSuite before 7.4.2-rev36 and 7.6.x before 7.6.0-rev23 allows remote authenticated users to execute arbitrary SQL commands via a crafted jslob API call.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?