VULHUB ™

In a PDC/BDC synchronization, the entire SAM database is sent encrypted between the Primary and Backup Domain Controllers. A unique RC4 cypher stream is created for each PDC/BDC synchronization. The LM and NT hashes are concatenated for each account and the same cypher stream is applied to each such block of data. In certain situations where a machine on the network has reset its Trust Account Password, the NT hash will be transmitted normally and the LM hash will be set to contain 16 bytes of zeroes (for the Trust Account only). As any value XORed with all zeroes returns the original value, the second half of the cypher stream is sent over the wire in plaintext in the LM hash field of the Trust Account portion of the synchronization. If an attacker can sniff the data on that segment, it is then possible to decrypt any LM hash from the SAM database using this second half of the keystream.

In a PDC/BDC synchronization, the entire SAM database is sent encrypted between the Primary and Backup Domain Controllers. A unique RC4 cypher stream is created for each PDC/BDC synchronization. The LM and NT hashes are concatenated for each account and the same cypher stream is applied to each such block of data. In certain situations where a machine on the network has reset its Trust Account Password, the NT hash will be transmitted normally and the LM hash will be set to contain 16 bytes of zeroes (for the Trust Account only). As any value XORed with all zeroes returns the original value, the second half of the cypher stream is sent over the wire in plaintext in the LM hash field of the Trust Account portion of the synchronization. If an attacker can sniff the data on that segment, it is then possible to decrypt any LM hash from the SAM database using this second half of the keystream.