KRACK: WPA2 encryption unsafe

The US CERT (United States Computer Emergency Readiness Team) has issued a warning about WPA2 WLAN networks: even if implemented correctly, private and enterprise WLAN networks are affected by some WPA2 vulnerabilities, even when using WPA-TKIP, AES-CCMP and GCMP. The problem depends on the log level: KRACKKey Reinstallation Attacks.

Good news ahead: You do not need WPA3. Only backwards compatible implementation is needed. Even if only one partner (access point or client) receives the update, the communication works and is safe against this attack capability.


US-CERT ist auf einige wichtige Verwundbarkeiten im 4-Wege-Handshake des Sicherheitsprotokolls Wi-Fi Protected Access II (WPA2) aufmerksam geworden. Die Auswirkungen der Ausnutzung dieser Schwachstellen umfassen Entschlüsselung, Paketwiederholung, TCP-Verbindungshijacking, HTTP-Inhaltsinjektion und andere.

All details are posted on and GitHub:

The WPA2 protocol uses a 4-way handshake. This handshake is executed when a client wants to join a protected Wi-Fi network, and checks the credentials. At the same time, the 4-way handshake also negotiates a new encryption key, which is used to encrypt all subsequent data traffic. Currently, all modern protected Wi-Fi networks use the 4-way handshake. This implies that all these networks are affected by one of these variants of the attack. The attack works, for example, against private and corporate Wi-Fi networks, against older WPA, and the latest WPA2 standard, and even against AES-only networks.

CVEs: CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13084, CVE-2017 -13086, CVE-2017-13087, CVE-2017-13088.
These can be used with macOS, OpenBSD, Linux and Android (version 6 or later).

One Comment

  1. Pingback: KRACK: WPA2 encryption unsafe |

Leave a comment