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.

Comments
LinkedIn: More Than 100 Million Member Accounts Exposed In 2012 Breach
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 !


Edge-DRsplash-10-edge-articles
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
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
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
Video
Cartoon
Current Issue
Enterprise Cybersecurity Plans in a Post-Pandemic World
Download the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3830
PUBLISHED: 2021-09-26
btcpayserver is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE-2021-21742
PUBLISHED: 2021-09-25
There is an information leak vulnerability in the message service app of a ZTE mobile phone. Due to improper parameter settings, attackers could use this vulnerability to obtain some sensitive information of users by accessing specific pages.
CVE-2020-20508
PUBLISHED: 2021-09-24
Shopkit v2.7 contains a reflective cross-site scripting (XSS) vulnerability in the /account/register component, which allows attackers to hijack user credentials via a crafted payload in the E-Mail text field.
CVE-2020-20514
PUBLISHED: 2021-09-24
A Cross-Site Request Forgery (CSRF) in Maccms v10 via admin.php/admin/admin/del/ids/<id>.html allows authenticated attackers to delete all users.
CVE-2016-6555
PUBLISHED: 2021-09-24
OpenNMS version 18.0.1 and prior are vulnerable to a stored XSS issue due to insufficient filtering of SNMP trap supplied data. By creating a malicious SNMP trap, an attacker can store an XSS payload which will trigger when a user of the web UI views the events list page. This issue was fixed in ver...