liveBook · Manning

Weak initialization vector

As explained in Hacking Cryptography

A weak initialization vector is a WEP IV whose byte pattern creates exploitable statistical leakage about the secret key during RC4 key scheduling.

A weak initialization vector (IV) is a WEP IV whose bytes trigger statistical leakage during RC4 key scheduling. In the FMS attack, the pattern [L, 255, X] targets key byte L; X is any one-byte value. Repeated weak IVs make that key byte more likely to appear as the first keystream byte. section 4.3.2

The attack turns the weakness into key recovery:

  • Observe IVs in cleartext and collect packets using the target pattern. section 4.3.2

Message volume determines reliability

A Go test recovers "helloworld123" with 50,000 weak-IV packets. Reducing the volume to 500 produces incorrect bytes such as 0x94, 0x2c, and 0x95, demonstrating that the leakage is statistical rather than deterministic.

How Hacking Cryptography covers it

How deep it goes
Traces IV selection, RC4 KSA leakage, keystream extraction, frequency ranking, and message-volume failure cases.
Examples
Uses [L, 255, X], a Go packet generator, RC4 recovery code, and tests with 50,000 versus 500 packets.
What it assumes
Assumes RC4 key scheduling, keystreams, WEP IVs, known plaintext, and frequency-based inference.
What you can do after
Diagnose WEP exposure and implement or reproduce statistical recovery of preshared-key bytes from weak-IV traffic.
How it connects
Connects WEP, RC4, the FMS attack, keystreams, known plaintext, RC4 KSA, and preshared keys.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Hacking Cryptography. The section links point to the parts of the book it draws on.