Last Updated: 2017-10-16 22:15:12 UTC
by Johannes Ullrich (Version: 1)
Starting yesterday, word of a new attack against WPA2 started to take over security news feeds. This "Key Reinstallation Attack" (aka KRACK) can be used to substantially weaken many WPA2 implementations.
The web site created by the discoverer of the attack does explain the issues around this problem quite well, so I just want to point out some of the highlights :
- access points as well as clients should be patched, but the main target are clients.
- This attack is particuarlly serious for Linux clients (Android). A specific implemention issue in these clients can lead to an all "0" encryption key being used.
- There are a few variants of the attack. All WPA2 implementations are affected by them in some form
- The POC implementation has not been made public yet, and there is no simple to use tool yet to launch the attack. But the paper about the vulnerability should contain sufficient details to create such a tool.
So what can you do?
- Patch. Once patches become available, apply them expediciously.
- If possible, do not just rely on WPA2 for security. SSL / IPSec can provide an additional layer of defense
- Use wired networks if possible (always a good idea)
This attack doesn't affect public access points as much. These types of access points do not usually use WPA2 in the first place, and if they do it is typically more for billing then to protect user traffic.
I expect an easy to use attack tool to be published within a few weeks, at which point you should have updated at least your clients. The tricky part will be legacy clients for which you wont easily find patches.
AES-CCMP is less vulnerable then WPA-TKIP or GCMP. But even with AES-CCMP, the attacker may be able to decrypt packets. Just packet injection is less likely with AES-CCMP. So I do not consider AES-CCMP a "quick fix", but a "necessary hardening" of the installion.
You will not need to change your WPA2 passphrase. This will easy upgrades. But of course, changing your passphrase may be a good idea anyway.
Lance Spitzner from SANS Securing the Human put together a nice blog post to inform non techincal users about the impact of this vulnerability: