Bitzu

CPSA ยท Windows passwords, vulnerabilities and hardening

LANMAN, NTLMv1 and NTLMv2: stored hashes vs network responses

How each stores or exchanges credentials and why LANMAN and NTLMv1 are weak.

Key points

  • LM hash: upper-cases, caps at 14 characters, splits into two 7-character halves hashed independently, no salt.
  • NT hash: unsalted MD4 of the password.
  • NTLMv1, NTLMv2: network challenge-response built from the NT hash; NTLMv2 adds client-chosen data and a timestamp, so it is much harder to attack.
  • Modern Windows stores no LM hash by default; the Refuse LM and NTLM level rejects the old responses.

Source: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/network-security-do-not-store-lan-manager-hash-value-on-next-password-change

Practice questions

Single choice

Why is the LAN Manager hash so much weaker than the NT hash?

  1. It upper-cases the password and hashes two 7-character halves separately
  2. It stores the password in plain text beside the hash
  3. It uses a short per-user salt that attackers can guess
  4. It is sent over the network in clear text on every logon
Show answer

Answer: A. It upper-cases the password and hashes two 7-character halves separately

Upper-casing and splitting into two independent 7-character halves shrinks the search space drastically, and neither half is salted. Length is capped at 14, which is a limit, not the main flaw.

Select all that apply

Which statements about Windows credential hashes are correct?

  1. Two accounts with the same password have the same NT hash
  2. NTLMv2 responses include client-chosen data, defeating precomputed response tables
  3. Current Windows does not store the LM hash by default
  4. The NT hash is salted per user in the SAM
  5. The LM hash keeps the original upper and lower case
Show answer

Answer: A. Two accounts with the same password have the same NT hash, B. NTLMv2 responses include client-chosen data, defeating precomputed response tables, C. Current Windows does not store the LM hash by default

The NT hash has no salt, so equal passwords give equal hashes. NTLMv2 mixes in client data, and current Windows does not keep the LM hash by default. No Windows version stores per-user salted NT hashes.

True or false

True or false: moving from NTLMv1 to NTLMv2 means the NT hash stored in the SAM is now salted.

Show answer

Answer: False

False. NTLMv2 changes the network challenge-response, not the stored hash. The NT hash stays an unsalted MD4 of the password.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More CPSA topics in this module