WEP Attacks and Exploitation
What you'll learn: How WEP's broken RC4 implementation allows attackers to recover encryption keys by collecting wireless packets.
The Fatal Flaw in WEP
WEP (Wired Equivalent Privacy) was the first wireless encryption standard, but it contains catastrophic cryptographic flaws. The protocol uses the RC4 stream cipher, which would be reasonably secure—except WEP reuses the same encryption key and pairs it with a 24-bit Initialization Vector (IV) to generate different keystreams. Since the IV is only 24 bits, it cycles through all possible values after roughly 5,000 packets on a busy network.
How the Attack Works
Think of WEP like a door lock where the key pattern eventually repeats. When the same IV is reused with the same key, identical keystreams are generated. Attackers capture these packets and use statistical analysis to find patterns.
The attack process:
- IV Collection: Capture thousands of packets containing different IVs
- Weak IV Identification: Some IVs leak information about the key
- Statistical Analysis: Use tools that perform mathematical correlation on the collected data
- Key Recovery: Extract the actual WEP key (typically within minutes)
Tools like aircrack-ng automate this process, requiring only 20,000-50,000 captured packets—easily achievable on any active network. Attackers can even speed this up by injecting packets to force more IV generation.
Why It's Unfixable
The flaw isn't in RC4 itself, but in how WEP implements it. The short IV length combined with lack of replay protection creates a mathematical certainty: given enough packets, the key will be recovered. No amount of patching can fix this fundamental design error.
Key Takeaway: WEP's RC4 implementation is cryptographically broken due to IV reuse and weak statistical properties—attackers can passively collect packets and mathematically derive the encryption key in minutes, making WEP completely unsuitable for protecting any network.