Daily Archives: October 18, 2017

WPA2 KRACK Vulnerability: What you need to know

Last Sunday, the early signs of a vulnerability disclosure affecting the extensively used Wi-Fi protected access (WPA2) protocol were evident. The next day, disclosure of the vulnerability lead to more details. The vulnerability was discovered by  two researchers Mathy Vanhoef and Frank Piessens of the Katholieke Universiteit Leuven (KU Leuven) while examining OpenBSD’s implementation of the WPA2 four way handshake.

Why should this vulnerability be considered important?
On Monday 16th October, the KRACK (key re-installation attacks) vulnerability was disclosed. This vulnerability was found within the implementation of the WPA2 protocol rather than any single device making it’s impact much more widespread. For example, vulnerable devices include Windows, OpenBSD (if not already patched against it), Linux, Apple iOS, Apple macOS and Google Android.

If exploited this vulnerability could allow decryption, packet replay, TCP connection hijacking and if WPA-TKIP (defined) or GCMP (explained) are used; the attacker can inject packets (defined) into a victim’s data, forging web traffic.

How can an attacker exploit this vulnerability?
To exploit the vulnerability an attacker must be within range of a vulnerable Wi-Fi network in order to perform a man in the middle attack (MiTM)(defined). This means that this vulnerability cannot be exploited over the Internet.

This vulnerability occurs since the initial four way handshake is used to generate a strong and unique key to encrypt the traffic between wireless devices. A handshake is used to authenticate two entities (in this example a wireless router and a wireless device wishing to connect to it) and to establish the a new key used to communicate.

The attacker needs to manipulate the key exchange (described below) by replaying cryptographic handshake messages (which blocks the message reaching the client device) causing it to be re-sent during the third step of the four way handshake. This is allowed since wireless communication is not 100% reliable e.g. a data packet could be lost or dropped and the router will re-send the third part of the handshake. This is allowed to occur multiple times if necessary. Each time the handshake is re-sent the attacker can use it to gather how cryptographic nonces (defined here and here) are created (since replay counters and nonces are reset) and use this to undermine the entire encryption scheme.

How can I protect myself from this vulnerability?
AS described in this CERT knowledge base article.; updates from vendors will be released in the coming days and weeks. Apple (currently a beta update) and Microsoft already have updates available. OpenBSD also resolved this issue before the disclosure this week.

Microsoft within the information they published for the vulnerability discusses how when a Windows device enters a low power state the vulnerable functionality of the wireless connection is passed to the underlying Wi-Fi hardware. For this reason they recommend contacting the vendor of that Wi-Fi hardware to request updated drivers (defined).

Links to affected hardware vendors are available from this ICASI Multi-Vendor Vulnerability Disclosure statement. Intel’ security advisory with relevant driver updates is here. The wireless vendor, Edimax also posted a statement with further updates to follow. A detailed but easy to use list of many vendors responses is here. Since I use an Asus router, the best response I could locate is here.

======
Update: 21st October 2017:
Cisco have published a security advisory relating to the KRACK vulnerability for its wireless products. At the time of writing no patches were available but the advisory does contain a workaround for some of the affected products.
======

The above updates are software fixes but updates will also be made available for devices in the form of firmware updates e.g. for wireless routers, smartphones and Internet of Things (IoT)(defined) devices. For any wireless devices you own, please check with the manufacturer/vendor for available updates with the above CERT article and vendor response list detailing many of the common vendors.

Thank you.

Infineon TPM Chips Patched Against Disclosed Vulnerability

With the release of Microsoft’s security updates last week; Infineon published a security advisory relating to a vulnerability discovered by security researchers in 2012.

Why should this vulnerability be considered important?
The vulnerable hardware is mostly to be found within corporate computers from manufacturers such as HP, Fujitsu and Lenovo. Google Chromebooks, routers and some Internet of Things (IoT)(defined). The vulnerability allows an attacker to determine a private (defined) encryption key when it has been generated by a vulnerable TPM (Trusted Platform Module) using only the public key (defined). Once the private key has been obtained it can be used by an attacker to decrypt the contents of a Microsoft BitLocker encrypted hard drive, to digitally sign fake software releases, to sign malware (making it appear more legitimate) as well impersonating the legitimate owner of the private key.

This vulnerability also affects cryptographic smart cards, security tokens and other secure hardware chips manufactured by Infineon. An estimate 760k devices are thought to be vulnerable while the true number could be up to three times that amount.

While the researchers were able to verify an attacker could derive the private key from 1024 and 2048 but public key, they were unable to do so for 4096 bit key since “a 4096-bit RSA key is not practically factorizable now, but “may become so, if the attack is improved.” For 1024 and 2048 bit keys, the factorisation can be easily parallelised by x number of CPUs, reducing the time taken by x times (where x is the number of cores a CPU has) allowing completion in hour or days.

How can I protect myself from this vulnerability?
Microsoft’s advisory provides the recommended steps for systems using Windows or other Microsoft products e.g. Active Directory Certificate Services (ADCS), Active Directory Directory Services (ADDS) (among others). The updates they recommend are only a workaround for the vulnerability. The vulnerability must still be resolved by applying updates to the vulnerable TPM chips. This advice also includes clearing the TPM and re-generating the necessary keys only after applying the updates from Microsoft.

Similarly Google made available Chrome OS M60 to mitigate this vulnerability. Further links to other affected vendors are listed below:

Fujitsu

HP Customer Support

HP Enterprise Support

Lenovo

Toshiba

Thank you.