CVE-2019-9499
The implementations of EAP-PWD in wpa_supplicant EAP Peer do not validate the scalar and element values in EAP-pwd-Commit
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The implementations of EAP-PWD in wpa_supplicant EAP Peer, when built against a crypto library missing explicit validation on imported elements, do not validate the scalar and element values in EAP-pwd-Commit. An attacker may complete authentication, session key and control of the data connection with a client. Both hostapd with SAE support and wpa_supplicant with SAE support prior to and including version 2.4 are affected. Both hostapd with EAP-pwd support and wpa_supplicant with EAP-pwd support prior to and including version 2.7 are affected.
Timeline
- CVE published
- Record last updated
Affected versions
- Wi-Fi Alliance hostapd with EAP-pwd support
From 2.7 · through 2.7
- Wi-Fi Alliance wpa_supplicant with EAP-pwd support
From 2.7 · through 2.7
- Wi-Fi Alliance hostapd with SAE support
From 2.4 · through 2.4
- Wi-Fi Alliance wpa_supplicant with SAE support
From 2.4 · through 2.4