Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

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
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5124
PUBLISHED: 2020-01-25
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.50005. A specially crafted pixel shader can cause a denial of service. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered fro...
CVE-2019-5146
PUBLISHED: 2020-01-25
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13025.10004. A specially crafted pixel shader can cause a denial of service. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered fro...
CVE-2019-5147
PUBLISHED: 2020-01-25
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13003.1007. A specially crafted pixel shader can cause a denial of service. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered from...
CVE-2019-5183
PUBLISHED: 2020-01-25
An exploitable type confusion vulnerability exists in AMD ATIDXX64.DLL driver, versions 26.20.13031.10003, 26.20.13031.15006 and 26.20.13031.18002. A specially crafted pixel shader can cause a type confusion issue, leading to potential code execution. An attacker can provide a specially crafted shad...
CVE-2020-5226
PUBLISHED: 2020-01-24
Cross-site scripting in SimpleSAMLphp before version 1.18.4. The www/erroreport.php script allows error reports to be submitted and sent to the system administrator. Starting with SimpleSAMLphp 1.18.0, a new SimpleSAML\Utils\EMail class was introduced to handle sending emails, implemented as a wrapp...