Red Hat Bugzilla – Bug 1278377
CVE-2015-5315 wpa_supplicant: EAP-pwd missing last fragment length validation
Last modified: 2015-11-11 06:50:45 EST
The following flaw was reported in hostapd:
A vulnerability was found in EAP-pwd server and peer implementation used in hostapd and wpa_supplicant, respectively. When an incoming EAP-pwd message is fragmented, the remaining reassembly buffer length was not checked for the last fragment (but was checked for other fragments). This allowed a suitably constructed last fragment frame to try to add extra data that would go beyond the buffer. The length validation code in wpabuf_put_data() prevents an actual buffer write overflow from occurring, but this results in process termination.
For wpa_supplicant with EAP-pwd enabled in a network configuration profile, this could allow a denial of service attack by an attacker within radio range.
wpa_supplicant v1.0-v2.5 with CONFIG_EAP_PWD=y in the build configuration (wpa_supplicant/.config) and EAP-pwd enabled in a network profile at runtime.
- Remove CONFIG_EAP_PWD=y from build configuration
- Disable EAP-pwd in runtime configuration
The related issue in hostapd is filed under CVE-2015-5314.
Created attachment 1090024 [details]
EAP-pwd peer: Fix last fragment length validation
Created attachment 1090025 [details]
EAP-pwd server: Fix last fragment length validation
Affected code does not exist in wpa_supplicant versions in Red Hat Enterprise Linux 6 and earlier. The wpa_supplicant packages in Red Hat Enterprise Linux 7 and Fedora are not built with the CONFIG_EAP_PWD configuration option and hence are also unaffected.
Not vulnerable. This issue did not affect the versions of wpa_supplicant as shipped with Red Hat Enterprise Linux 5, 6, and 7.