Attacks/Breaches

6/6/2012
11:47 AM
50%
50%

LinkedIn Users: Change Password Now

Attackers appear to have obtained--and may have already decrypted--at least 6.5 million LinkedIn passwords.

All users of the LinkedIn social network should immediately change their password.

Security experts began broadcasting that warning Wednesday after reports emerged that nearly 6.5 million LinkedIn password hashes--encrypted using SHA1, but not salted--had been posted to a Russian hacking forum on Monday, together with a request to help decrypt them.

Hackers have already reported breaking 163,267 of the passwords, reported Norwegian news outlet Dagen IT, which Wednesday broke the news of the LinkedIn password breach.

LinkedIn confirmed that it's investigating the potential password breach. "Our team is currently looking into reports of stolen passwords. Stay tuned for more," read a Wednesday tweet from LinkedIn News.

[ Read about how hackers accessed a Romney Webmail account. See Romney Campaign Investigates Hotmail Account Hack. ]

What should LinkedIn users do? "First change your LinkedIn password. Then prepare for scam emails about Linkedin password changes, linking to phishing sites. Will happen," said Mikko Hypponen, chief research officer at F-Secure, via Twitter.

Security expert Per Thorsheim tweeted that he'd reviewed the uploaded password hashes and recovered at least 300,000 of them. "The number of [occurrences] of 'linkedin' in those passwords leave little doubt about the origin. Change password NOW!" Meanwhile, a post from the Security Ninja website's Twitter feed noted that "after getting the list of @linkedin hashes and hashing my old pwd with no salt there is a match for the hash in the list." Accordingly, it said that it was "best to assume the worst and change your password."

Evidently, LinkedIn didn't salt its passwords--a practice recommended by security experts that involves adding a unique string to each password before encrypting it. Had the passwords been salted, it would have made them more difficult for attackers to reverse the SHA1 password hashes. In fact, attackers may have already decrypted the passwords, and they may also have users' passwords and email addresses. "Although the data which has been released so far does not include associated email addresses, it is reasonable to assume that such information may be in the hands of the criminals," said Graham Cluley, senior technology consultant at Sophos, in a blog post.

The Computer Emergency Response Team of Finland (CERT-FI) Wednesday warned that many more than the 6,458,020 uploaded password hashes are likely to have been obtained by attackers. "Not all LinkedIn passwords have been published, but it is likely that an attacker is in possession of the rest of the passwords," it said.

According to LinkedIn, as of March 31, 2012, it had 161 million members.

CERT-FI also advised anyone who had reused their LinkedIn password on another site to immediately change it there as well, since it will be at risk of being hacked by anyone who downloads and reverses the uploaded LinkedIn password hashes.

More and more organizations are considering development of an in-house threat intelligence program, dedicating staff and other resources to deep inspection and correlation of network and application data and activity. In our Threat Intelligence: What You Really Need to Know report, we examine the drivers for implementing an in-house threat intelligence program, the issues around staffing and costs, and the tools necessary to do the job effectively. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
GR8Day
50%
50%
GR8Day,
User Rank: Apprentice
6/7/2012 | 3:31:25 PM
re: LinkedIn Users: Change Password Now
I am surprised a social networks who is geared for the professional would not be more security conscious. I am a member and would like to see them take some steps to provide me with additional layers of protection for access to my account verification without unreasonable complexity. It would be great to see them just as some of the other leading companies in their respective verticals giving us the perfect balance between security and user experience by moving to the use of 2FA (two-factor authentication) mobile or other, as a form of a token where the user is asked to telesign into their account by entering a one-time PIN code which is delivered to your phone via SMS or voice. I wish really wish more organizations would start implementing 2FA.
Number 6
50%
50%
Number 6,
User Rank: Apprentice
6/6/2012 | 6:18:22 PM
re: LinkedIn Users: Change Password Now
Nice of LinkedIn to not mention this to their users when they sign on (so far).
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Mueller Probe Yields Hacking Indictments for 12 Russian Military Officers
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/13/2018
10 Ways to Protect Protocols That Aren't DNS
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/16/2018
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
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12959
PUBLISHED: 2018-07-19
The approveAndCall function of a smart contract implementation for Aditus (ADI), an Ethereum ERC20 token, allows attackers to steal assets (e.g., transfer all contract balances into their account).
CVE-2018-14336
PUBLISHED: 2018-07-19
TP-Link WR840N devices allow remote attackers to cause a denial of service (connectivity loss) via a series of packets with random MAC addresses.
CVE-2018-10620
PUBLISHED: 2018-07-19
AVEVA InduSoft Web Studio v8.1 and v8.1SP1, and InTouch Machine Edition v2017 8.1 and v2017 8.1 SP1 a remote user could send a carefully crafted packet to exploit a stack-based buffer overflow vulnerability during tag, alarm, or event related actions such as read and write, with potential for code t...
CVE-2018-14423
PUBLISHED: 2018-07-19
Division-by-zero vulnerabilities in the functions pi_next_pcrl, pi_next_cprl, and pi_next_rpcl in lib/openjp3d/pi.c in OpenJPEG through 2.3.0 allow remote attackers to cause a denial of service (application crash).
CVE-2018-3857
PUBLISHED: 2018-07-19
An exploitable heap overflow exists in the TIFF parsing functionality of Canvas Draw version 4.0.0. A specially crafted TIFF image processed via the application can lead to an out-of-bounds write, overwriting arbitrary data. An attacker can deliver a TIFF image to trigger this vulnerability and gain...