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.

LinkedIn: More Than 100 Million Member Accounts Exposed In 2012 Breach
Newest First  |  Oldest First  |  Threaded View
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. :--)))
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 :--))
User Rank: Ninja
5/24/2016 | 11:24:15 AM
Re: A Timing Puzzlement
That is true. Nobody actually cared that LinkedIn was hacked. 
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.
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.
User Rank: Ninja
5/23/2016 | 9:12:39 AM
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.
User Rank: Ninja
5/23/2016 | 8:59:17 AM
Re: A Timing Puzzlement
Yes, I believe you are correct.
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?

User Rank: Apprentice
5/19/2016 | 9:33:51 AM
Thanks for your post !

I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
How Machine Learning, AI & Deep Learning Improve Cybersecurity
Machine intelligence is influencing all aspects of cybersecurity. Organizations are implementing AI-based security to analyze event data using ML models that identify attack patterns and increase automation. Before security teams can take advantage of AI and ML tools, they need to know what is possible. This report covers: -How to assess the vendor's AI/ML claims -Defining success criteria for AI/ML implementations -Challenges when implementing AI
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-09-26
An issue was discovered in Zimbra Collaboration (ZCS) 8.8.x and 9.x (e.g., 8.8.15). The Sudo configuration permits the zimbra user to execute the NGINX binary as root with arbitrary parameters. As part of its intended functionality, NGINX can load a user-defined configuration file, which includes pl...
PUBLISHED: 2022-09-26
An issue was discovered in Zimbra Collaboration (ZCS) 8.8.15 and 9.0. An attacker can upload arbitrary files through amavisd via a cpio loophole (extraction to /opt/zimbra/jetty/webapps/zimbra/public) that can lead to incorrect access to any other user accounts. Zimbra recommends pax over cpio. Also...
PUBLISHED: 2022-09-25
Use After Free in GitHub repository vim/vim prior to 9.0.0579.
PUBLISHED: 2022-09-25
registerFont in FontMetrics.php in Dompdf before 2.0.1 allows remote file inclusion because a URI validation failure does not halt font registration, as demonstrated by a @font-face rule.
PUBLISHED: 2022-09-25
Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0577.