{"id":1879,"date":"2017-10-16T13:07:13","date_gmt":"2017-10-16T13:07:13","guid":{"rendered":"http:\/\/www.mtin.net\/blog\/?p=1879"},"modified":"2017-10-16T13:07:13","modified_gmt":"2017-10-16T13:07:13","slug":"vulnerability-in-wpa2","status":"publish","type":"post","link":"http:\/\/www.mtin.net\/blog\/vulnerability-in-wpa2\/","title":{"rendered":"Vulnerability in WPA2"},"content":{"rendered":"

https:\/\/arstechnica.com\/information-technology\/2017\/10\/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping\/<\/a><\/p>\n

An air of unease set into the security circles on Sunday as they prepared for the disclosure of high-severity vulnerabilities in the\u00a0Wi-Fi Protected Access II protocol<\/a>\u00a0that make it possible for attackers to eavesdrop Wi-Fi traffic passing between computers and access points.<\/em><\/p>\n

The proof-of-concept exploit is called KRACK, short for Key Reinstallation Attacks. The research has been a closely guarded secret for weeks ahead of a coordinated disclosure that’s scheduled for <\/em>8am Monday, East Coast time. An advisory the\u00a0US CERT<\/a>\u00a0recently distributed to about 100 organizations described the research this way:<\/em><\/p>\n

US-CERT has become aware of several key management vulnerabilities in the 4-way handshake of the Wi-Fi Protected Access II (WPA2) security protocol. The impact of exploiting these vulnerabilities includes decryption, packet replay, TCP connection hijacking, HTTP content injection, and others. Note that as protocol-level issues, most or all correct implementations of the standard will be affected. The CERT\/CC and the reporting researcher KU Leuven, will be publicly disclosing these vulnerabilities on 16 October 2017.<\/p><\/blockquote>\n

 <\/p>\n

From Mikrotik:<\/p>\n

\n
On October 16. CERT\/CC\/ICASI released a public announcement about discovered vulnerabilities in WPA2 handshake protocols that affect most WiFi users and all vendors world wide.
\nRouterOS v6.39.3, v6.40.4, v6.41rc are not affected!
\nIt is important to note that the vulnerability is discovered in the protocol itself, so even a correct implementation is affected.
\nThese organizations did contact us earlier, so we have already released fixed versions that address the outlined issues. Not all of the discovered vulnerabilities directly impact RouterOS users, or even apply to RouterOS, but we did follow all recommendations and improved the key exchange process according to the guidelines we received from the organizations who discovered the issue.
\nWe released fixed versions last week, so if you upgrade your devices routinely, no further action is required.
\nCWE-323
\nCVE-2017-13077
\nCVE-2017-13078
\nCVE-2017-13079
\nCVE-2017-13080
\nCVE-2017-13081
\nCVE-2017-13082
\nCVE-2017-13083
\nCVE-2017-13084
\nCVE-2017-13085
\nCVE-2017-13086
\nCVE-2017-13087<\/div>\n<\/div>\n