Aug 232012
 

Windows Password Hints are stored in cleartext in Windows Registry! Great Post by http://profile.typepad.com/jclaudius

Source: http://blog.spiderlabs.com/2012/08/all-your-password-hints-are-belong-to-us.html

 

All Your Password Hints Are Belong to Us

This past weekend I ended up coming into the SpiderLabs office and “nerded out” with my good friend Ryan Reynolds to follow-up on the research we released at DEFCON and BlackHatthis year.  As some of you may already know, our research was focused on corruption of LM and NTLM password hashes when they were extracted from the Windows registry (specifically, the SAM) by many tools.

In the process of going through one our test cases on a Windows 8 machine on Saturday, we stumbled across a new key (“UserPasswordHint”) that we had not seen before in the SAM database.  To both of us, this seemed like a rather odd, but intriguing key that would be cool to explore a bit more “at some point”.

Well… being the impatient weirdo that I am, I could not wait and dove in headfirst as soon as I got home that night.  This blog post will cover some of the details on how to extract/decode User Password Hints from the Windows registry and how I extended Metasploit’s Hashdump tools to incorporate this information.

Inside the Registry Data

For starters, the “UserPasswordHint” key on Windows 8 (and Windows 7) is stored in the following location:

HKLM\SAM\SAM\Domains\Account\Users\<userkey>\UserPasswordHint

If you’re running with SYSTEM access (you can use your imagination here), you can read this key easily by doing a reg query like so:

Win8_sam_registry

In first looking at the storage location here, I was a little disappointed thinking that the hint was encrypted in some way until I noticed the pattern of zeros.  Having dealt with a fair amount of PHP malware in the last couple months, one of things the “baddies” do is chunk up their payload data into individual characters and then encode them in their ASCII numerical representation.  Well in looking at this registry value, it seemed to follow a similar approach, so I wrote a little decoder in Ruby to see if I could learn this users password hint.

Here is the decode method I whipped up to do this:

Decode_method

Now you can use the value stored for this user and translate it back to the clear-text hint, like so:

Decoded_message

Although this stuff looked a bit unreadable on the surface we can now see that it can clearly be decoded and could be used by tools that extract information from the SAM.  This seems like it would be very helpful for penetration testers by giving them more insight into what the user’s password might be, so I decided to take it one step further.

Extending Metasploit’s Hashdump Tools

In our recent hash corruption research, we ended up making a number of changes to the Metasploit Hashdump tools (hashdump.rb and smart_hashdump.rb) and became very familiar with how they work.   As such, it just made sense to try integrating user password hint decoding with these tools so I sent a GitHub pull request on Sunday night to the Metasploit team to add this functionality.

Here is a preview of what these new additions will give users when dump hashes from a Meterpreter session:

Windows_hints2

As of yesterday, these password hint extraction features were merged into the Metasploit Project.  I would like to extend a special thanks to @_sinn3r and @TheLightCosine for their ideas, de-turding and review of my code.  Also, props to @_sinn3r for pointing out that Window XP also stores user password hints in another location in the registry in the decoded form (this was also included in the recent Metasploit improvements).

Parting Thoughts

I had a lot of fun with this little detour through the Windows Registry for a couple hours.  If you use these tools and these new fangled hints help you out in some way, I would love to hear your story.

That is all for now.  I hope to have more Windows Registry hijinks and other “hax” to talk about here in the near future, so please stay tuned.