Michael Meierruth (3/6/2013) paul.knibbs (3/6/2013) SQLCharger (3/6/2013)
Would this also work with Windows
hashes as well?
That would be even more scary (if someone manages to get your Windows hash from a server).
There's no reason why it wouldn't, but getting the Windows hash of your password from the server isn't a trivial thing--you usually need admin access in order to read the SAM database, and if you already have that level of access, why do you care about hacking somebody else's password?
It's for finding those people who use the same password everywhere else...
Or for escalating privileges, especially in a domain. Standard attack pattern:
1. Gain admin rights to a workstation or server.
2. Dump LSA Secrets. This gives you the password in plaintext for any services.
3. See what rights/group memberships those accounts have. They are now in your set of accounts to use for further compromise.
4. Dump the hashes from that system.
5. Use rainbow tables to gain the password from said hashes.
6. See what rights/group memberships those accounts have. They are also now in your set of accounts to use for further compromise.
7. If you've got a Domain Admin level at this point, you're set. You own the domain (and technically, the forest, meaning also every domain in said forest).
8. If you don't have an account with the level of privs that you want, spiderweb to other systems, trying the accounts you've captured and repeating steps 1-7.
K. Brian Kelley