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

5/19/2016
08:45 AM
100%
0%

LinkedIn: More Than 100 Million Member Accounts Exposed In 2012 Breach

LinkedIn data theft is likely to be much worse than expected with additional data being released now.

The ghost of the past has come back to haunt LinkedIn: the 2012 data breach that led to an unauthorized release of member details is now rearing its head again with an additional set of member data exposed. LinkedIn announced that it's now invalidating the hacked passwords and alerting those members to reset their passwords.

The social media site yesterday clarified that the additional data released from the 2012 breach was likely to be the “email and hashed password combinations of more than 100 million LinkedIn members from that same theft in 2012.” 

Online magazine Motherboard this week reported that a hacker is trying to sell the account information of 117 million LinkedIn users. Motherboard said the hacker has indicated there are 167 million accounts in the hacked database, of which 117 million have both emails and encrypted passwords. Back in 2012, details of only around 6.5 million accounts were posted online, says Motherboard.

LinkedIn is now invalidating passwords for all accounts not changed before the 2012 breach and trying to identify and block suspicious activity on affected accounts.

For more details, click here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:28:17 AM
Nobody cases LinkedIn hacked
For me, people did not seem to care that LinkedIn was hacked in 2012. It did not bother anybody that their resumes and connections was disposed to others. The only problem is the username password, since we all use those in other sites too. :--)))
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:25:28 AM
Re: Persistant
Agree. I am in the same both. Not in LinkedIn but in other sites, I still user the password I defined 5 years ago :--))
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:24:15 AM
Re: A Timing Puzzlement
That is true. Nobody actually cared that LinkedIn was hacked. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:23:10 AM
Re: Thanks
Yes, it is an old case that we had to remember again. It does not go away.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
5/24/2016 | 11:22:11 AM
hashed password
 

Hass in one way so there is no encryption/decryption on the hash. For me this is the most secure way to deal with the passwords but if your password is simple has can not protect you.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/23/2016 | 9:12:39 AM
Persistant
This promotes the best practice of users changing their password on a regular basis. I would think that unaware users from 2012 would still be using their original password if there was not a forced change.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/23/2016 | 8:59:17 AM
Re: A Timing Puzzlement
Yes, I believe you are correct.
dieselnerd
50%
50%
dieselnerd,
User Rank: Strategist
5/19/2016 | 12:36:28 PM
A Timing Puzzlement
"LinkedIn is now invalidating passwords for all accounts not changed before the 2012 breach..."

Wouldn't that be not changed after the 2012 breach?

 
Fleety
50%
50%
Fleety,
User Rank: Apprentice
5/19/2016 | 9:33:51 AM
Thanks
Thanks for your post !
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/22/2020
How an Industry Consortium Can Reinvent Security Solution Testing
Henry Harrison, Co-founder & Chief Technology Officer, Garrison,  5/21/2020
Is Zero Trust the Best Answer to the COVID-19 Lockdown?
Dan Blum, Cybersecurity & Risk Management Strategist,  5/20/2020
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
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13616
PUBLISHED: 2020-05-26
The boost ASIO wrapper in net/asio.cpp in Pichi before 1.3.0 lacks TLS hostname verification.
CVE-2020-13614
PUBLISHED: 2020-05-26
An issue was discovered in ssl.c in Axel before 2.17.8. The TLS implementation lacks hostname verification.
CVE-2020-13615
PUBLISHED: 2020-05-26
lib/QoreSocket.cpp in Qore before 0.9.4.2 lacks hostname verification for X.509 certificates.
CVE-2020-9046
PUBLISHED: 2020-05-26
A vulnerability in all versions of Kantech EntraPass Editions could potentially allow an authorized low-privileged user to gain full system-level privileges by replacing critical files with specifically crafted files.
CVE-2020-12388
PUBLISHED: 2020-05-26
The Firefox content processes did not sufficiently lockdown access control which could result in a sandbox escape. *Note: this issue only affects Firefox on Windows operating systems.*. This vulnerability affects Firefox ESR < 68.8 and Firefox < 76.