How KRACK made it past scrutiny of researchers: IEEE's standards specs are hard to access and handshake and encryption protocols were vetted separately
The big news in crypto today is the KRACK attack on WPA2 protected WiFi networks. Discovered by Mathy Vanhoef and Frank Piessens at KU Leuven …
Context & Ripple Effects
The US CERT advisory on KRACK landed a day before this piece, and Mathy Vanhoef and Frank Piessens' disclosure of the WPA2 exploits is what forced the question of how such a basic key-reinstallation bug survived years of expert review. The answer offered here is procedural, not cryptographic: IEEE's specifications are hard for outsiders to obtain, and the four-way handshake and the underlying encryption were vetted as separate workstreams, so nobody audited their composition.
That process critique matters because the corpus shows Wi-Fi security failures repeating across generations of the standard — the Dragonblood vulnerabilities hit the WiFi Alliance's freshly launched WPA3 within two years, Frag Attacks reached back across 24 years of devices, and a 2023 flaw in IEEE 802.11 itself allowed malicious TCP packet injection.
First-order effects
- Vendors shipping WPA2 implementations face an immediate patching burden against the CERT advisory, while unpatched routers and clients remain open to eavesdropping, connection hijacking, and injection until fixed.
- IEEE's standards process takes direct reputational damage: the restricted access and siloed vetting that let KRACK through are now part of the public record alongside the bug itself.
Second-order effects
- The WiFi Alliance's push toward WPA3 becomes the industry's visible remediation path, but Dragonblood's disclosure shows the successor standard inherits review risk, forcing another patch cycle rather than closing the chapter.
- Security researchers gain leverage to demand open access to protocol specifications, since the KRACK post-mortem makes closed specs a demonstrable audit failure rather than a theoretical concern.
Third-order effects
- If the pattern holds — WPA2, then WPA3, then 802.11 itself yielding flaws — the structural lesson is that Wi-Fi security needs whole-protocol verification, including cross-layer interactions, rather than per-component review by small credentialed groups.
- Standards bodies that keep specifications paywalled or fragmented invite exactly this class of missed bug, pushing the ecosystem toward openly published, formally analyzable protocol definitions as the price of credibility.
The trend: Wi-Fi security is shifting from reactive patch-by-patch disclosure toward demands for open specification access and whole-protocol verification, as successive standards — WPA2, WPA3, 802.11 — keep failing under independent scrutiny.