Summary
Multiple security issues and vulnerabilities within the WPA2 standard have been identified and publicized by Mr. Mathy Vanhoef of KU Leuven. These vulnerabilities may allow the reinstallation of a pairwise transient key, a group key, or an integrity key on either a wireless client or a wireless access point (AP). In consequence, an attacker could establish a man-in-the-middle position between AP and client facilitating packet decryption and injection.
Update A / Revision 2 - 2017-11-09
* Added a detailed list of affected products
Update B / Revision 3 - 2018-09-24
* Added firmware update information, see section "Solution"
Details
Impact
PHOENIX CONTACT embedded devices running in AP mode are not affected by these vulnerabilities. If devices are used in client or repeater mode, an attacker could in theory decrypt any packet sent by the client. Devices of the FL WLAN 110x, 210x, and 510x product families are only affected to a very limited extent. With these devices, only data packets sent within three seconds after key renewal could possibly be decrypted by a successful attacker. In general, if TCP SYN packets are decrypted, this can be used to hijack TCP connections and inject malicious traffic into unencrypted protocols. However, to perform the attack, the attacker must be significantly closer to the WLAN client than the access point. In industrial or indoor applications, the attacker would have to be inside the plant. A successful external attack therefore seems to be very difficult. Furthermore, the WPA2 password cannot be compromised using a KRACK attack. It is not possible for the attacker to gain full access to the network. However, note that if WPA-TKIP is used instead of AES-CCMP, the impact of this vulnerability is much more severe, because an attacker can then not only decrypt packets, but also forge and inject packets directly into the WLAN.
Remediation / Solution
PHOENIX CONTACT is actively working on these vulnerabilities. CERT@VDE will update this advisory as soon as further significant details are provided by the vendor, especially with information about patches provided.
For PHOENIX CONTACT devices running Microsoft Windows, we recommend to apply the security update provided by Microsoft external link. If you are using WPA-TKIP in your WLAN, you should switch to AES-CCMP immediately.
This advisory will be updated as further details become available.
For the following products a firmware update addressing the issues is available for download on the Download tab of the corresponding product page on our website:
Products: FL EPA 2, FL EPA 2 RSMA
Fixed Firmware: 1.53 or higher
Released: 06/2018
Products: FL WLAN 5100, FL WLAN 5101, FL WLAN 5102, FL WLAN 5110, FL WLAN 5111
Fixed Firmware: FW 3.06 or higher
Released: 06/2018
Products: FL WLAN 1100, FL WLAN 1101, FL WLAN 2100, FL WLAN 2101
Fixed Firmware: FW 2.21 or higher
Released: 06/2018
Vulnerabilities 3
-
Unscored —
Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Pairwise Transient Key (PTK) Temporal Key (TK) durin…
-
Unscored —
Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group Temporal Key (GTK) during the four-way handsha…
-
Unscored —
Wi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group Temporal Key (GTK) during the group key handsh…
Revision history
-
#5
Fix: version space, removed ia, version term
-
#4
Fix: correct certvde domain, added self-reference
-
#3
Updated Solution.
-
#2
Updated affected products.
-
#1
Initial revision.
References
-
Phoenix Contact PSIRT
https://www.phoenixcontact.com/de-de/service-und-support/psirt
-
CERT@VDE Security Advisories for Phoenix Contact
https://certvde.com/en/advisories/vendor/phoenixcontact/
-
VDE-2017-003: PHOENIX CONTACT: WLAN enabled devices utilising WPA2 encryption - HTML
https://certvde.com/en/advisories/VDE-2017-003/