Risk

RockYou Lawsuit Settlement Leaves Question Marks On Breach Liability

Settlement is small, but legal experts say case might pave way for more lawsuits against breached companies

When Alan Claridge's personal information was compromised in the breach of data from RockYou in 2009, he sued the company for damages. Last week, after two years in litigation, a settlement was proposed -- and legal experts say it might prop the door open for more lawsuits.

According to the proposed settlement, the judgment in Claridge's favor awards him only $2,000 -- though his lawyers get $290,000. The financially troubled RockYou claimed inability to pay the judgment.

The proposed settlement might not make Claridge a rich man, but legal experts say he might have made his point about the liability of companies that lose customer data through breaches, according to a commentary by Data Privacy Monitor.

"Because only the plaintiff’s claims would be dismissed with prejudice, other putative class members may still assert claims for monetary damages," the report says. "It is important to note that the proposed settlement does not vacate the district court’s April 2011 decision, leaving it of record for other plaintiffs to reference in future putative class actions."

Claridge was one of 32 million users whose data was breached in the hack of RockYou in December 2009, and his class-action lawsuit alleges negligence in the company's security practices. According to the lawsuit, RockYou stored all user account data in plain text in its database, unencrypted. The company also only required a five-character password, and did not permit those passwords to use special characters. RockYou used email to send the passwords out.

The crackers breached the RockYou database using an SQL vulnerability that had been documented for more 10 years, according to the lawsuit. The security breach also revealed passwords to outside websites, such as Facebook and MySpace. RockyYou didn't notify users for days after the breach, and incorrectly reported that it affected only older applications. Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10091
PUBLISHED: 2019-03-21
AudioCodes IP phone 420HD devices using firmware version 2.2.12.126 allow XSS.
CVE-2018-10093
PUBLISHED: 2019-03-21
AudioCodes IP phone 420HD devices using firmware version 2.2.12.126 allow Remote Code Execution.
CVE-2017-2659
PUBLISHED: 2019-03-21
It was found that dropbear before version 2013.59 with GSSAPI leaks whether given username is valid or invalid. When an invalid username is given, the GSSAPI authentication failure was incorrectly counted towards the maximum allowed number of password attempts.
CVE-2017-16231
PUBLISHED: 2019-03-21
** DISPUTED ** In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of st...
CVE-2017-16232
PUBLISHED: 2019-03-21
** DISPUTED ** LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue.