A dictionary attack is method of cracking passwords by exploiting the fact that people tend to used easily-remembered words and phrases for passwords. A password cracker assembles a list of commonly-used password, often starting with the words in the dictionary, and attempts each password. Dictionary attacks are usually employed before resorting to a Brute Force Attack because they're much faster to perform. Dictionary attacks can even be employed to determine passwords obscured with a hash function.
While there are legitimate uses for a dictionary attack, like recovering forgotten passwords or verifying that passwords are secure, dictionary attacks are usually used for nefarious purposes, so understanding the process is necessary for protecting yourself against it.
I learned about dictionary attacks in a programming class in college.
- 1 Process
- 2 Defenses
- 3 Links
This section describes the steps necessary to perform a dictionary attack.
Step 1: Obtain a List of Commonly Used Passwords
This is particularly easy since many crackers have already done the hard work and compiled lists of commonly used passwords. Here is an example list:
Step 2: Try Each Password
A basic computer program is created to attempt every password in the dictionary on the specified user account. Since most log-in gateways protect against multiple incorrect password attempts, a password cracker will usually have to steal a user table with the passwords.
Step 3: Steal a Password Table
This is the most difficult part of the attack, as system administrators don't just give away user's passwords. Obtaining a password table means being able to defeat a system's security or buying a password table from someone who already has. Since it is a security flaw for even admins to know a user's password, the passwords in the table are almost always obfuscated through a one-way hash function. So, when you look at a password table, it may look something like this:
In this example, the passwords have been run through an MD5 hash function which cannot be reversed. When a user logs in, the computer will first apply the same hash to the password they typed in, and compare it with the one on-file to ensure a match. This way, the plaintext password is only ever known by the user. So then, how can a password cracker ever determine a user's password without a Brute Force Attack? This is where the dictionary attack comes into play.
Step 4: Run the Same Hash On the Dictionary Passwords
Hash functions used to obfuscate passwords cannot be reversed, but they can be repeated. To do this, a cracker must know the exact same hash function used to obfuscate the passwords in the stolen password table. This isn't too difficult, since only a few are commonly used. From here, the cracker runs all the commonly used passwords through the same hash function and gets a list of the hashes for each of the passwords.
|Common Password||MD5 Hash|
I should point out that the MD5 hash function is not a cryptographically secure hash function and should never be used to store passwords. I'm just using it for this example.
Step 5: Compare Against the Password Table
Once the dictionary of hashes has been generated, the cracker need simply look for matches in the hashes between the stolen password table and their dictionary. A match indicates that the user chose the password in the table.
|User||Password||Match From Dictionary|
This method will identify every password in the stolen password table that matches one in the dictionary of commonly used passwords, which, in common practice, is often over half.
Since computers are very fast at generating hash functions and comparing values between two tables, a dictionary attack with millions of commonly used passwords can be carried out against a table of millions of user passwords in a matter of minutes.
This section details the ways to protect yourself from a dictionary attack.
It should go without saying that a system administrator should eliminate access to the password table for all but the most trusted personnel. As a user, you should also be wary of supplying passwords to any system where administrators don't vigilantly protect the password table. This is also a general rule for all information, no matter how encrypted you might feel your data is, never allow people to have access to it. You never know if it will fall into the hands of a clever person.
Use Unique Passwords
Only use unique passwords that won't show up in the cracker's dictionary. If you're not sure if your password is unique, open a browser (in secret mode) and do a Google search of your password in quotes. If there are any results, you should probably choose a more complicated password. Also, adding a number to the end of a common word will not make it safe, even if there isn't a Google hit. Multiple dictionaries can be created with permutations of existing passwords. For example, a cracker could make a copy of their dictionary and append the number 1 to the end of each password and run a dictionary attack on that as well and it wouldn't add much time to the process. Best practice is a number or symbol in the middle of a word.
Use Uncommon Characters
Older systems rarely allow for this, but modern systems do. When you create a password, include a character that is not found on your keyboard. You can do this when typing in your password by holding down the ALT key on your keyboard then typing the character's number on your keypad (the numbers on the side of your keyboard, not the top), then release the ALT key. For example, ALT+175 gives you this character, "»". Few password dictionaries are going to include even a single password with that character in it, so your password will be safe from a dictionary attack.
In order to combat dictionary attacks, most modern password tables first apply a salt to passwords before sending them through a hash function. A salt is a modification to a password so that it will yield a completely different hash from what is expected. For example, the passwords below have been salted by adding a question mark to the beginning of them before being hashed, which yields a completely different MD5 hash.
|Common Password||MD5 Hash||Salted Password||Salted Hash|
When using a salt, the program that handles user passwords must not only apply the salt when storing the password into the password table, but it must also apply the salt to the password each time a user logs in to make sure it will match the hash in the password table.
A salted password table adds a layer of security because, in order for a dictionary attack to work, the dictionary of hashes must be re-generated with the passwords and the salt. So, if the cracker doesn't know the salt, all of the passwords will fail to match the hash. Naturally, the particular salt being used should never be disclosed, but, if a cracker defeated a system's security well enough to make a copy of the password table, they probably also made a copy of the program that adds the salt and can determine if from that.
Even if the cracker doesn't know the salt, by using a Brute Force Attack on a salted password hash, a cracker can usually determine what the salt is based on the results. For example, if the cracker brute forced two of the passwords from the table and found that they both began with a question mark, they could probably guess that it was the salt. Because of this, a salt will not stop a cracker, but it might slow them down long enough for the administrator to take counter-measures, like forcing everyone to change their password.
- en.wikipedia.org/wiki/Dictionary_attack - Wikipedia.