A Cambridge University researcher successfully used Google to unearth a password used by an attacker to compromise its security blog.

The attacker created an account in Wordpress when he attacked the Light the Blue Touch Paper blog, the online journal of the Computer Laboratory at Cambridge University. Wordpress stores passwords as MD5 hashes without salting, a process that adds length and complexity to password hashes.

Curious to know what this password might be, Cambridge researcher Steven Murdoch tried a dictionary attack in both English and Russian (the likely native language of the attacker).

Rather than building a rainbow table that maps passwords to hashes for a more exhaustive range of possible inputs, Murdoch plugged the MD5 into Google which revealed multiple sites featuring the word "Anthony", the attacker's password. The approach hit on a result because the hash was in the URL.

"This makes a lot of sense - I've even written code which does the same. When I needed to store a file, indexed by a key, a simple option is to make the filename the key's MD5 hash. This avoids the need to escape any potentially dangerous user input and is very resistant to accidental collisions," Murdoch notes (http://www.lightbluetouchpaper.org/2007/11/16/google-as-a-password-cracker).

The new variant on Google hacking illustrates a couple of important points: that Google is indexing password hashes, albeit inadvertently, as well as everything else; and that MD5 hashes without salting are next to useless.

Murdoch's posting on his findings has sparked a lively thread (http://www.lightbluetouchpaper.org/2007/11/16/google-as-a-password-cracker) on the Light the Blue Touch Paper blog. One respondent created a utility (http://utilitymill.com/utility/Goog_Your_Hash) that lets users find out if their passwords are safe.

Using hard to guess passwords is simple common sense that somehow often gets overlooked. As one poster notes, searching for hashes of common default passwords such as "admin" throws up database dumps and the likes. ®

Related stories

Hackers find clever new way to hose Google users (6 March 2008)
http://www.theregister.co.uk/2008/03/06/googe_iframe_piggybacking/
cDc automates Google Hacking (22 February 2008)
http://www.theregister.co.uk/2008/02/22/goolag_scanner/
Camouflaged code threatens security apps (4 January 2008)
http://www.theregister.co.uk/2008/01/04/code_camouflage/
ID profiles worth far more than credit card details to crooks (22 November 2007)
http://www.theregister.co.uk/2007/11/22/id_profile_trade/
Google Code Search peers into programs' flaws (8 October 2006)
http://www.theregister.co.uk/2006/10/08/google_code_search_peers_into_program_flaws/
Google-based malware search tool surfaces (18 July 2006)
http://www.theregister.co.uk/2006/07/18/malware_search/
Rainbow warriors crack password hashes (10 November 2005)
http://www.theregister.co.uk/2005/11/10/password_hashes/
Desktop search and malware: friend or foe? (13 October 2005)
http://www.theregister.co.uk/2005/10/13/desktop_search_malware_risk/
Hacking Google for fun and profit (4 April 2005)
http://www.theregister.co.uk/2005/04/04/google_hacking/