Bug 1491697 (CVE-2017-13081) - CVE-2017-13081 wpa_supplicant: Reinstallation of the integrity group key in the group key handshake
Summary: CVE-2017-13081 wpa_supplicant: Reinstallation of the integrity group key in t...
Status: CLOSED NOTABUG
Alias: CVE-2017-13081
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact: Ken Benoit
URL:
Whiteboard: impact=important,public=20171016,repo...
Keywords: Security
Depends On: 1502588 1502589
Blocks: 1491701 1516327
TreeView+ depends on / blocked
 
Reported: 2017-09-14 12:32 UTC by Adam Mariš
Modified: 2019-06-08 22:21 UTC (History)
9 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2017-10-19 08:45:42 UTC


Attachments (Terms of Use)

Description Adam Mariš 2017-09-14 12:32:02 UTC
A new exploitation technique called key reinstallation attacks used to break Wi-Fi handshakes that negotiate session keys was discovered. These attacks target the Wi-Fi/WPA2 standard. An adversary can trick a client or Access Point (AP) into reinstalling an already-in use integrity group key in the group key handshake. While reinstalling the already in-use key, the associated packet number (sometimes also called nonce) and receive replay counter is reset. This causes nonce reuse, voiding any security the underlying encryption protocol is supposed to provide. For example, it allows decryption or injection of frames, and enables an attacker to replay frames.

Comment 1 Adam Mariš 2017-09-14 12:32:06 UTC
Acknowledgments:

Name: CERT
Upstream: Mathy Vanhoef (University of Leuven)

Comment 8 Andrej Nemec 2017-10-16 09:42:12 UTC
Created hostapd tracking bugs for this issue:

Affects: fedora-all [bug 1502588]


Created wpa_supplicant tracking bugs for this issue:

Affects: fedora-all [bug 1502589]

Comment 12 Stefan Cornelius 2017-10-18 08:49:45 UTC
Statement:

This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7, as CONFIG_IEEE80211W was not enabled.


Note You need to log in before you can comment on or make changes to this bug.