CVE-2017-13088: Medium severity android vulnerability
Wi-Fi Protected Access (WPA and WPA2) that support 802.11v allows reinstallation of the Integrity Group Temporal Key (IGTK) when processing a Wireless Network Management (WNM) Sleep Mode Response frame, allowing an attacker within radio range to replay frames from access points to clients.
Other sources
Wi-Fi Protected Access II (WPA2) handshake traffic can be manipulated to induce nonce and session key reuse, resulting in key reinstallation by a victim wireless access point (AP) or client. After establishing a man-in-the-middle position between an AP and client, an attacker can selectively manipulate the timing and transmission of messages in the WPA2 Wireless Network Management (WNM) Sleep Mode handshake, resulting in out-of-sequence reception or retransmission of messages.
An attacker within the wireless communications range of an affected AP and client may leverage these vulnerabilities to conduct attacks that are dependent on the data confidentiality protocol being used. Attacks may include arbitrary packet decryption and injection, TCP connection hijacking, HTTP content injection, or the replay of unicast, broadcast, and multicast frames.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-13088?
CVE-2017-13088 is considered a high-severity vulnerability due to its potential for compromising user data through replay attacks.
How do I fix CVE-2017-13088?
To fix CVE-2017-13088, update to the latest version of the affected software that has patched the vulnerability.
Which operating systems are affected by CVE-2017-13088?
CVE-2017-13088 affects certain versions of Android, Ubuntu, Debian, FreeBSD, OpenSUSE, and Red Hat Enterprise Linux.
What type of attack is possible due to CVE-2017-13088?
CVE-2017-13088 allows attackers to perform replay attacks by reinstalling the Integrity Group Temporal Key (IGTK) from a compromised network.
Is there a workaround for CVE-2017-13088?
A common workaround for CVE-2017-13088 includes disabling the affected network configurations, although updating to secure versions is highly recommended.