NTLM
.DGoYJB0B.png)
Theory
A common error people do is mix LM, NT, NTLM, Net-NTLM etc. Let's make things clear. There are hashing formats used to store user passwords: LM, NT. And there are authentication protocols used to authenticate users to remote resources: LM, NTLMv1, and NTLMv2.
- LM hash and NT hash will refer to the hashing formats
- LM, NTLM(v1), and NTLMv2, will refer to the authentication protocols
- LMv1 and LMv2 are response formats that clients return when responding to NTLM_CHALLENGE NTLMv1 and NTLMv2 messages, respectively.
Yes.. this is confusing, but hey go tell this to Microsoft 😤
The LM (LAN Manager) and NTLM (New Technology LM) authentication protocols are widely used in today's Microsoft environments (but mostly NTLM). It relies on a challenge-response scheme based on three messages to authenticate. In order to prove its identity, the authenticating client is asked to compute a response based on multiple variables including:
- a random challenge sent by the server in a
CHALLENGE_MESSAGE - a secret key that is the hash of the user's password
The following table details the secret key used by each authentication protocols and the cryptographic algorithm used to compute the response (source).
| Authentication protocol | Algorithm (for the protocol) | Secret key |
|---|---|---|
| LM | DES-ECB | LM hash |
| NTLM | DES-ECB | NT hash |
| NTLMv2 | HMAC-MD5 | NT hash |
The following table details the hashing algorithm used by each hashing format in Windows that allows the system to transform the user's password in a non-reversible format.
| Hashing format | Algorithm (for the hash) |
|---|---|
| LM hash | based on DES (learn more) |
| NT hash | MD4 |
This is meant to protect the user's password from eavesdropping by implementing the "zero-knowledge proof" concept. Attackers capturing authentication (during a man-in-the-middle attack for example) would not be able to use the response to authenticate. In theory, they could only try to retrieve the user's password from an NTLM hash by operating two expensive (in time and resources) bruteforce attacks:
- a bruteforce attack against the LM/NTLM response to retrieve the LM or NT hash it was derivated from
- if found, a bruteforce/dictionary attack against the NT hash to retrieve the user's password
Read the capture.md article for more insight
Read the cracking.md article for more insight
The problem is that Microsoft has poorly implemented the zero-knowledge proof concept in the LM and NTLM protocols. The LM or NT hash is used "as is" to compute the response. This means an attacker knowing an LM or NT hash could use it to authenticate as a user without knowing the user's password. This technique is called Pass the hash.
Read the pth.md article for more insight
Attackers could also rely on forced authentications and phishing to relay incoming authentications.
Read the mitm-and-coerced-authentications article for more insight
Read the relay.md article for more insight