Computer Network & Network Security System — Network Security, NEC licence examination syllabus (Nepal Engineering Council).
Securing Wireless LANs: WEP (and why it failed)
One of the most famous cautionary tales in network security — a "secure" standard that turned out to be badly broken.
WEP (Wired Equivalent Privacy) was Wi-Fi's original attempt at security — using a shared key to encrypt wireless traffic, trying to make wireless "as secure as" a physical wired connection.
⚠️ Why WEP Failed
Short, reused keysUsed a small "initialization vector" that repeated often enough to be statistically attacked.
Weak encryptionThe underlying cipher (RC4) was implemented in a way that leaked patterns attackers could exploit.
ResultWEP keys could be cracked in minutes with freely available tools — it was formally deprecated and replaced by WPA/WPA2/WPA3.
💡 One-liner: "Why was WEP eventually abandoned?" → Its short, frequently-repeated initialization vectors combined with weak RC4 implementation made it practically crackable within minutes — a landmark case study in why "encrypted" doesn't automatically mean "secure."
How quickly the IV actually repeats
"Repeated often enough to be statistically attacked" understates it dramatically. The IV is 24 bits:
Possible IV values: 2²⁴ = 16,777,216
By the birthday bound, a repeat becomes likely after
roughly 1.2 × √16,777,216 ≈ 4,915 packets.
At 1000 packets per second that is about FIVE SECONDS.
Exhausting every IV takes under 5 hours.
Two packets sharing an IV and key produce keystreams that are identical, so XORing the two ciphertexts cancels the keystream entirely and leaves the two plaintexts combined — recoverable with basic analysis. WEP did not fail because the attack was subtle; it failed because a busy network hands the attacker what they need within minutes of listening.
💡 The general lesson matters more than WEP: a stream cipher's key must never be reused across messages. That is the whole purpose of the IV, and 24 bits was far too few — an error of design rather than of implementation, which is why patching WEP was impossible and it had to be replaced.
The other two failures
⚠️ Beyond the IV
Integrity checkWEP used CRC-32, which is designed to catch accidental errors and is linear — so an attacker can alter the message and adjust the checksum to match. It detects noise, not adversaries.
Key managementOne shared key for every device, changed by hand. In practice it was never changed, and any departing user retained it forever.
💡 The CRC point is the one worth generalising: an error-detecting code is not a message authentication code. CRC assumes errors are random; a MAC assumes they are chosen by someone trying to fool you. Substituting one for the other is a recurring real-world mistake, and a good exam answer names the distinction.
What replaced it
WPA was designed to run on existing WEP hardware, so it kept RC4 but added a longer IV and a proper message integrity check with per-packet key mixing. WPA2 made the clean break to AES with a genuine MAC, which is why it is the answer to "what should be used instead".
💡 A one-line summary that earns marks: WEP failed because a 24-bit IV made key reuse inevitable within minutes, and because CRC-32 could be forged. The fixes were a longer IV, per-packet keys, a real MAC, and eventually a stronger cipher.
Syllabus points
WEP operation
WEP weaknesses
Create a free account to tick topics off, take notes as you read, watch the video lessons and get a day-by-day study plan built around your exam date.