Just Say No To KRACK

Did you wake up this morning to discover that Wi-Fi security is fundamentally broken? Before you toss your phone away, smash your router, and move to a cabin in the woods, it might be good to take stock of the actual issue.

The WPA2 KRACK vulnerability is pretty serious. An on-site attacker can decrypt and replay client-to-AP traffic. Not Good. But while this cuts through the basic confidence in WPA2, it’s important to get context into how easy this exploit is to pull off (not very), and if patches are available to solve the issue.

Andrew von Nagy has done a great job in compiling many of the company responses to the exploit. The good news is that Microsoft, Aruba, Ubiquiti, and Meraki already have patches in the wild. The bad news? There’s a lot of companies who don’t and who knows how long it will take to implement patches when they do arrive.

KRACK is bad, but keeping updated on patches, looking for MITM attacks on-site, and using https will go a long way in terms of prevention.

Andrew von Nagy comments:

What’s the TL;DR? There are 9 vulnerabilities that are client related and 1 that is AP / Infrastructure related. All are implementation issues, meaning software patching can fix them! Of the 9 CVE’s related to clients, ALL can be mitigated with AP / Infrastructure updates as a workaround, but the infrastructure won’t be able to determine if failure is from packet loss issues or attack. The long-term fix is definitely client software patching. The 1 CVE related to AP / Infrastructure is related to 802.11r Fast Transition – if you have it enabled you should patch ASAP. If not, no big deal.

Read More

About the author

Rich Stroffolino

Rich has been a tech enthusiast since he first used the speech simulator on a Magnavox Odyssey². Current areas of interest include ZFS, the false hopes of memristors, and the oral history of Transmeta.

Leave a Comment