[aklug] KRACK attack on WiFi at the protocol level (*all* clients affected)

[Royce Williams]

Flaw with the protocol itself - so *anything* speaking Wi-Fi will need
to be patched, including the long tail of legacy, EOL, and cheap IoT
gear that will likely never be patched. Assume all Wi-Fi networks are
observable until then (core mitigations is to use a VPN). Long term,
recommend adding to RFPs for any gear (not just wireless) to ensure
updates for X period of time.

Main announcement:
    https://www.krackattacks.com/

Paper with background:
    https://papers.mathyvanhoef.com/ccs2017.pdf

I will assemble what I know here:
    http://www.techsolvency.com/story-so-far/krackattack/

Other good meta-threads and summaries, keep an eye on these:
    https://github.com/kristate/krackinfo
    https://www.reddit.com/r/sysadmin/comments/76lj5q/this_is_a_core_protocollevel_flaw_in_wpa2_wifi/


Per-vendor stuff:

Aruba:
    http://community.arubanetworks.com/t5/Wireless-Access/Core-level-protocol-flaw-in-WPA2/td-p/310038
    http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-007_FAQ_Rev-1.pdfhttp://www.arubanetworks.com/support-services/security-bulletins/

wpa_supplicant:
    https://w1.fi/cgit/hostap/commit/


News:

https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/
https://www.alexhudson.com/2017/10/15/wpa2-broken-krack-now/


CVEs:

CWE-323
CVE-2017-13077
CVE-2017-13078
CVE-2017-13079
CVE-2017-13080
CVE-2017-13081
CVE-2017-13082
CVE-2017-13083
CVE-2017-13084
CVE-2017-13085
CVE-2017-13086
CVE-2017-13087

Royce