Opened 6 years ago

Closed 6 years ago

#10994 closed task (fixed)

Rebase wpa_supplicant security patch to include new vulnerability fix

Reported by: Douglas R. Reno Owned by: blfs-book
Priority: high Milestone: 8.3
Component: BOOK Version: SVN
Severity: normal Keywords:


From the oss-security mailing list:

Published: August 8, 2018
- CVE-2018-14526
Latest version available from:


A vulnerability was found in how wpa_supplicant processes EAPOL-Key
frames. It is possible for an attacker to modify the frame in a way that
makes wpa_supplicant decrypt the Key Data field without requiring a
valid MIC value in the frame, i.e., without the frame being
authenticated. This has a potential issue in the case where WPA2/RSN
style of EAPOL-Key construction is used with TKIP negotiated as the
pairwise cipher. It should be noted that WPA2 is not supposed to be used
with TKIP as the pairwise cipher. Instead, CCMP is expected to be used
and with that pairwise cipher, this vulnerability is not applicable in

When TKIP is negotiated as the pairwise cipher, the EAPOL-Key Key Data
field is encrypted using RC4. This vulnerability allows unauthenticated
EAPOL-Key frames to be processed and due to the RC4 design, this makes
it possible for an attacker to modify the plaintext version of the Key
Data field with bitwise XOR operations without knowing the contents.
This can be used to cause a denial of service attack by modifying
GTK/IGTK on the station (without the attacker learning any of the keys)
which would prevent the station from accepting received group-addressed
frames. Furthermore, this might be abused by making wpa_supplicant act
as a decryption oracle to try to recover some of the Key Data payload
(GTK/IGTK) to get knowledge of the group encryption keys.

Full recovery of the group encryption keys requires multiple attempts
(128 connection attempts per octet) and each attempt results in
disconnection due to a failure to complete the 4-way handshake. These
failures can result in the AP/network getting disabled temporarily or
even permanently (requiring user action to re-enable) which may make it
impractical to perform the attack to recover the keys before the AP has
already changes the group keys. By default, wpa_supplicant is enforcing
at minimum a ten second wait time between each failed connection
attempt, i.e., over 20 minutes waiting to recover each octet while
hostapd AP implementation uses 10 minute default for GTK rekeying when
using TKIP. With such timing behavior, practical attack would need large
number of impacted stations to be trying to connect to the same AP to be
able to recover sufficient information from the GTK to be able to
determine the key before it gets changed.

Vulnerable versions/configurations

All wpa_supplicant versions.


Thanks to Mathy Vanhoef of the imec-DistriNet research group of KU
Leuven for discovering and reporting this issue.

Possible mitigation steps

- Remove TKIP as an allowed pairwise cipher in RSN/WPA2 networks. This
  can be done also on the AP side.

- Merge the following commits to wpa_supplicant and rebuild:

  WPA: Ignore unauthenticated encrypted EAPOL-Key data

  This patch is available from

- Update to wpa_supplicant v2.7 or newer, once available

We should probably rebase the patch to include

Change History (1)

comment:1 by Bruce Dubbs, 6 years ago

Resolution: fixed
Status: newclosed

Updated the patch. Now wpa_supplicant-2.6-upstream_fixes-2.patch

Fixed at revision 20387 and patches commit 3786.

Note: See TracTickets for help on using tickets.