Determining if Your LinkedIn Password has Been Compromised
As reports have swirled throughout the day that approximately 6.5 million LinkedIn passwords have been leaked, security experts have been trying to figure out what happened, as well as checking to see if their own passwords have been compromised.
The process involves downloading the dataset of leaked passwords, converting your password into the encrypted format in which the passwords are displayed, and searching for the password in the dataset.
All of the leaked passwords are hashed, or encrypted using SHA-1, which converts the characters that make up the password into a 40-character hash. To find the hash that’s connected to your password, there are a variety of free SHA-1 conversion tools, including from websites such as Hash.online-convert.com; Sha1hash.com and this free online hash converter.
Some experts warn about using such online conversion tools, however. Dave Pack is a director at LogRhythm, a log management and IT security firm, who says some of the online conversion websites hold logs of hashes that have been calculated, so he warns about using such tools if your LinkedIn password is also used as a credential for other websites.
Another way to create a hash and avoid using a conversion tool is to use a command line transcript that creates the hashtag automatically and searches for it directly in the datadump. Those command line transcripts are specific to individual operating systems.
For users of the online conversion tool, the next step is to download the set of hashed passwords. The dataset can be accessed from a variety of sites. One that continues to host the dataset is here at MediaFire. Once the file is downloaded, simply search within the text file for the password in its SHA-1 hashed format.
If the hashed password is not found, it may be listed in another form within the database. The hackers seem to have replaced the first five characters of a portion of the hashed passwords with five zeros. Pack believes those indicate hashes that have already been converted back into their native password form. To search for the hashed passwords, replace the first five characters of the hashed password with five zeros and search the document again.
Pack also warns that even if your password does not appear on the list, users should still assume that their password could be compromised. Many times, he says, hackers will only release a portion of the compromised data to prove that they have it. That means passwords of other LinkendIn users could be compromised, even if they do not appear in the dataset.
No matter if your password is on the list or not, Pack recommends changing your LinkedIn password to a strong password that has a combination of numbers, as well as upper and lowercase letters. He recommends against using common words found in a dictionary for a password.
As of now, there is no evidence that there is any link between the hashed passwords and which users those passwords belong to, but Pack says that too should not be taken for granted. It’s possible that whoever released the data could have access to user information linked to those passwords.
Gene McCully, president of StackFrame, a computer software and security firm in Florida, searched and found his unique password in the database. He’s surprised LinkedIn did not modify the passwords using a technique called “salting” to further protect the passwords. “If it had been salted, it would have made it a less dangerous leak,” he says. Salting is the process of adding user-specific data to hashed passwords, making it harder to convert the hashes into the actual password.
“That’s one of the most shocking things of this whole situation is that there are unsalted passwords,” says Pack. “It says a lot about the overall security of the site.”
Without salted passwords, hackers can perform fairly simple SQL-injection attacks, which use web applications to gain insight into a database. In the company’s blogpost confirming the breach on Tuesday, LinkedIn officials say they have “just recently” added salting and hashing to the company’s current password databases.
Source: Network World (US)