7.2 Wireless Encryption

EC-Council Certified Ethical Hacker CEH

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 CEH Exam Format, Cost & Eligibility 1.2 The Five Phases of Ethical Hacking 1.3 Information Security Fundamentals 1.4 Ethical Hacking Concepts, Scope & Legal Framework 1.5 The CEH Domains & Your Study Priority Map

2 Reconnaissance, Footprinting, Scanning & Enumeration

2.1 Footprinting & Reconnaissance Concepts 2.2 Footprinting Sources & Techniques 2.3 Network Scanning Concepts 2.4 Banner Grabbing, OS Fingerprinting & Scanning Beyond IDS/Firewall 2.5 Enumeration 2.6 Vulnerability Scanning & Countermeasures

3 Vulnerability Analysis & System Hacking Phases

3.1 Vulnerability Analysis Concepts 3.2 System Hacking Methodology Overview 3.3 Gaining Access: Password Attack Concepts 3.4 Privilege Escalation Concepts 3.5 Maintaining Access: Backdoors, Rootkits & Persistence 3.6 Covering Tracks, Anti-Forensics & Blue-Team Detection

4 Malware Threats, Sniffing & Social Engineering

4.1 Malware Concepts and Taxonomy 4.2 Malware Analysis and Detection 4.3 Sniffing Concepts and Layer 2 Attacks 4.4 Sniffing Countermeasures and Detection 4.5 Social Engineering Types and Human Psychology 4.6 Social Engineering and Insider Threat Defenses

5 Network & Perimeter Hacking

5.1 Denial of Service and DDoS Attacks 5.2 Session Hijacking 5.3 Evading IDS and IPS (Defensive Focus) 5.4 Evading Firewalls 5.5 Evading Honeypots and Defensive Deception 5.6 Network Security Controls and Architecture 5.7 Packet Analysis and Secure Protocols for Defenders

6 Web Server & Web Application Hacking

6.1 Web Server Attacks & Hardening 6.2 OWASP Top 10 Overview 6.3 Injection: SQL Injection & Command Injection 6.4 Cross-Site Scripting (XSS) & CSRF 6.5 Authentication, Session & Access-Control Flaws 6.6 API & Web App Security Testing Concepts

7 Wireless Network Hacking

7.1 Wireless Concepts and Standards 7.2 Wireless Encryption 7.3 Wireless Threats and Attack Concepts 7.4 Wireless Security Countermeasures

8 Mobile Platform, IoT & OT Hacking

8.1 Mobile Platform Threats & Security Models 8.2 Mobile Attack Vectors & Risks 8.3 Mobile Device Management & Enterprise Defense 8.4 IoT Hacking Concepts & Defense 8.5 OT, ICS & SCADA Security

9 Cloud Computing & Cryptography

9.1 Cloud Computing Concepts 9.2 Cloud Threats & Attack Surfaces 9.3 Cloud Security Controls 9.4 Cryptography Fundamentals 9.5 PKI & Cryptographic Applications 9.6 Cryptanalysis, Crypto Attacks & Best Practices

7.2 Wireless Encryption

Key Takeaways Explain This Topic AI

WEP is broken because its 24-bit initialization vector reuses over time and RC4 key-scheduling weaknesses allow statistical key recovery from captured traffic

WPA introduced TKIP as a transitional firmware fix for WEP hardware, but TKIP still relies on RC4, is deprecated, and is disallowed in modern certifications

WPA2 mandates CCMP, which uses the AES block cipher for confidentiality and integrity and remains secure when configured with a strong passphrase

The WPA2 PSK 4-way handshake derives the session key from the passphrase; capturing the handshake (or a PMKID) enables an OFFLINE dictionary attack against weak passwords

WPA3-Personal replaces the PSK handshake with SAE (Dragonfly), a password-authenticated key exchange that resists offline dictionary attacks and adds forward secrecy and mandatory Protected Management Frames

Last updated: June 2026

The Evolution of Wireless Encryption

Wireless encryption protects the confidentiality and integrity of data over the air. CEH heavily tests why each generation was retired , not just their names. Remember that the cipher (encryption) is separate from the authentication mode (Open/PSK/Enterprise from 7.1); a single network configures both.

WEP — Wired Equivalent Privacy (Broken)

WEP used the RC4 stream cipher with a short, cleartext initialization vector (IV) of only 24 bits . With such a small IV space, the IV repeats on a busy network, and the FMS and later PTW attacks exploit weaknesses in RC4 key scheduling to recover the key statistically from enough captured frames — often in minutes. WEP also used a weak CRC-32 integrity check that does not detect deliberate tampering. WEP is cryptographically broken and must never be used.

WPA with TKIP (Transitional, Deprecated)

WPA (Wi-Fi Protected Access) was a stopgap so existing WEP hardware could be patched by firmware. It introduced TKIP (Temporal Key Integrity Protocol) , which adds per-packet key mixing, a 48-bit IV/sequence counter to stop replay, and a stronger Message Integrity Check (MIC, "Michael") . But TKIP still rides on RC4 and has known weaknesses (e.g., the Beck-Tews attack), so the Wi-Fi Alliance deprecated TKIP ; modern certifications disallow TKIP-only modes.

WPA2 with CCMP/AES (Secure When Configured Well)

WPA2 mandates CCMP (Counter Mode with Cipher Block Chaining Message Authentication Code Protocol) , built on the AES block cipher (128-bit). CCMP provides both confidentiality and integrity, with no practical break of the cipher itself. WPA2's residual exposure is the PSK 4-way handshake : a captured handshake (or a PMKID) lets an attacker attempt an offline guess of a weak passphrase. The cipher is sound — a weak password is the failure.

The WPA2 4-Way Handshake

The 4-way handshake is the heart of WPA/WPA2-PSK and the target of most WPA2 attacks. Both sides already know the Pairwise Master Key (PMK) , derived from the passphrase and SSID. The handshake proves each side knows the PMK and derives fresh session keys.

AP → client: sends the AP nonce ( ANonce ).

Client → AP: sends its nonce ( SNonce ) plus a MIC. The client can now compute the Pairwise Transient Key (PTK) from PMK + ANonce + SNonce + both MAC addresses.

AP → client: sends the Group Temporal Key (GTK) and a MIC, confirming it derived the same PTK.

Client → AP: acknowledges; encryption begins.

The attack: an attacker only needs to capture this exchange (messages 1-2 carry the nonces and MIC). With the SSID, nonces, and MAC addresses known, the attacker guesses passphrases offline — for each candidate, derive the PMK, compute the PTK, and check whether the resulting MIC matches the captured one. No interaction with the AP is needed during cracking, so rate-limiting and lockouts do not help; only passphrase entropy does. The PMKID (a value some APs place in the first frame) lets an attacker skip waiting for a client entirely and attack a single captured frame.

WPA3 with SAE (Current Best Practice)

WPA3-Personal replaces the PSK handshake exposure with SAE (Simultaneous Authentication of Equals) , a password-authenticated key exchange known as the Dragonfly handshake. SAE makes offline guessing infeasible: an attacker who captures the exchange cannot test passwords offline, only via slow online attempts. WPA3 also adds forward secrecy (a future password compromise does not decrypt past traffic) and mandatory Protected Management Frames (PMF / 802.11w) , which blunt deauthentication abuse. WPA3-Enterprise offers an optional 192-bit security mode for high-assurance environments.

Caveat the exam may probe: the 2019 Dragonblood research found that early WPA3 implementations were vulnerable to downgrade attacks (forcing a fallback to WPA2's crackable handshake) and side-channel timing/cache leaks. These are implementation flaws, not a break of SAE's design, and were addressed by patches and WPA3 transition-disable ; SAE remains the strongest option.

Encryption Comparison Table

Protocol Cipher / mode Key exchange Integrity Status Why retired / strength

WEP RC4 stream, 24-bit IV Static shared key CRC-32 (weak) Broken IV reuse + RC4 key-scheduling weakness allow key recovery

WPA (TKIP) RC4 + per-packet mixing PSK / 802.1X Michael MIC Deprecated Still RC4-based; known TKIP attacks; firmware-only stopgap

WPA2 (CCMP) AES-128 in CCMP PSK 4-way / 802.1X CCMP (AES-CBC-MAC) Acceptable Cipher sound; handshake/PMKID enables offline guessing of weak passwords

WPA3 (SAE) AES (CCMP/GCMP) SAE / 802.1X PMF mandatory Recommended SAE resists offline dictionary attacks; adds forward secrecy and PMF

Key Distinctions for the Exam

WEP is broken (the cipher fails); WPA-TKIP is deprecated (legacy, weak); WPA2-CCMP is sound but exposed by weak passphrases; WPA3-SAE is current best practice.

CCMP/AES vs TKIP/RC4: CCMP is the strong, mandatory WPA2/WPA3 choice; TKIP exists only for backward compatibility and should be disabled.

SAE vs PSK: both can use the same passphrase, but SAE removes the offline cracking path a captured handshake creates.

A WPA2 network in mixed/transitional mode that still allows TKIP weakens itself to the lowest common cipher — disable legacy fallbacks.