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.

Attacks/Breaches

Sony Sued Over PlayStation Network Hack

A class action lawsuit charges that Sony failing to protect personal information and credit card numbers of up to 77 million users.

10 Massive Security Breaches
(click image for larger view)
Slideshow: 10 Massive Security Breaches
Sony faces public condemnation as its PlayStation Network (PSN) outage enters its seventh day, combined with a security breach of users' personal information that may have exposed the credit card details of up to 77 million customers.

On Wednesday, Kristopher Johns, 36, of Birmingham, Ala., filed the first class action lawsuit, on behalf of all PSN users, in the U.S. District Court for the Northern District of California. The lawsuit alleges that Sony "failed to encrypt data and establish adequate firewalls to handle a server intrusion contingency, failed to provide prompt and adequate warnings of security breaches, and unreasonably delayed in bringing the PSN service back on line." It also accused Sony of violating the Payment Card Industry (PCI) security standard, which prohibits companies from storing cardholder data.

Sony pulled the plug on PSN and its Qriocity music service on Friday, three days after it discovered "an external intrusion," according to a blog post from Patrick Seybold, Sony's senior director of corporate communications and social media. The outage blocks users from playing online games as well as some users from accessing multiple services, including Netflix and Hulu Plus. At the time, Seybold said that Sony was attempting to resolve the situation quickly.

By Tuesday, Sony said that the PSN outage was continuing while it attempted to address a situation that was worse than it originally suspected. Namely, Sony's forensic investigation had discovered that a hacker had compromised the personal information of up to 77 million users.

In a letter sent to all PSN and Qriocity account holders, Sony said that "although we are still investigating the details of this incident, we believe that an unauthorized person has obtained the following information that you provided: name, address (city, state, zip), country, email address, birth date, PlayStation Network/Qriocity password and login, and handle/PSN online ID." In addition, the attacker may also have stolen users' purchase history, billing address, and password security questions.

Most alarmingly, however, "while there is no evidence at this time that credit card data was taken, we cannot rule out the possibility," said the Sony letter. "Out of an abundance of caution we are advising you that your credit card number (excluding security code) and expiration date may have been obtained."

What should Sony's customers do to protect themselves? "If you have used the same username/e-mail address with the same password in some other service, change the password now. When PSN comes back online, change your password there as well," said Mikko Hypponen, chief research officer at F-Secure, in an email. Security experts also recommend canceling any potentially compromised credit cards.

In response to the breach, Sony said it had engaged a major security firm to investigate the intrusion and that it was going to "strengthen our network infrastructure by re-building our system to provide you with greater protection of your personal information." According to Sony, "our teams are working around the clock on this, and services will be restored as soon as possible."

What exactly might Sony be rebuilding? "Details of the 'rebuild' are not forthcoming so it's hard to identify exactly what they are changing. In my experience with such security issues, however, I would note that complex systems that are built lacking security are often incredibly difficult to debug and patch with security if they aren't built on good foundations," said James Lyne, director of technology strategy at Sophos, in an email interview. "Often, security with such large-scale data processing systems needs to be built into the architecture," and if it isn't, he said, the simplest way to create a secure approach is to simply start from scratch.

On the other hand, "time is of the essence" for Sony, hence "tactical patching in the existing infrastructure--to avoid additional exploits--followed by a complete design review, is a good strategy," he said.

Sony has no doubt started by addressing how a hacker managed to--potentially--steal credit card details for up to 77 million people, which puts it in apparent violation of PCI. Regardless, Lyne said that companies can do better. "The practices required by standards such as PCI are 'decent practices' but I would argue a great deal more could be done to avoid extensive exposure of credit card information," he said. "It's time to apply the lessons learned over the past few years and raise the bar."

Applying lessons learned may not, however, be Sony's strong suit, owing to its reputation for security incidents that spiral into PR disasters, owing to a lack of transparency. Notably, Sony earned mass condemnation--and saw at least one class action lawsuit--in 2005, when it installed a hidden rootkit on users' PCs to block them from copying Sony music CDs. Antivirus firms quickly designated the software, which was extremely difficult to uninstall, as spyware, and set their software to nuke it.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...