Pass-the-Hash Attacks
What you'll learn: How attackers reuse captured password hashes to authenticate to other systems without ever cracking the original password.
The Core Idea
In Windows environments using NTLM authentication, passwords are stored and transmitted as hashed values (specifically, NTLM hashes). Here's the vulnerability: Windows doesn't always verify you know the actual password—it just checks if you have the correct hash.
Think of it like a hotel keycard system. Normally, you'd show ID at the front desk to get a keycard. But imagine if you could copy someone else's keycard and use it at any hotel door—without ever knowing their name or ID number. That's Pass-the-Hash: you steal the hash (the "keycard") from one compromised machine and present it to authenticate to other systems on the network.
How It Works
After gaining access to a system (covered in credential dumping lessons), attackers extract NTLM hashes from memory or security databases. Instead of spending time cracking these hashes to discover the plaintext password, they simply reuse the hash directly to authenticate to:
- SMB file shares
- Remote desktop sessions
- Windows admin shares (like
C$orADMIN$) - Other network services accepting NTLM
Tools like mimikatz, crackmapexec, or impacket's scripts can perform these attacks, effectively letting attackers move laterally across the network using stolen credentials—all without knowing a single password.
Why It's Dangerous
This technique bypasses password complexity requirements entirely. Even if a user has a 50-character randomly generated password, the hash is still reusable. This makes lateral movement rapid and stealthy once an attacker has compromised one system.
Key Takeaway: Pass-the-Hash exploits NTLM authentication's design by reusing captured hashes directly for authentication, enabling lateral movement without cracking passwords—making hash protection as critical as password security.