Описание
The EAP-pwd peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not clear the L (Length) and M (More) flags before determining if a response should be fragmented, which allows remote attackers to cause a denial of service (crash) via a crafted message.
The EAP-pwd peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not clear the L (Length) and M (More) flags before determining if a response should be fragmented, which allows remote attackers to cause a denial of service (crash) via a crafted message.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2015-4146
- https://security.gentoo.org/glsa/201606-17
- http://lists.opensuse.org/opensuse-updates/2015-06/msg00019.html
- http://w1.fi/security/2015-4/0005-EAP-pwd-peer-Fix-asymmetric-fragmentation-behavior.patch
- http://w1.fi/security/2015-4/eap-pwd-missing-payload-length-validation.txt
- http://www.debian.org/security/2015/dsa-3397
- http://www.openwall.com/lists/oss-security/2015/05/09/6
- http://www.openwall.com/lists/oss-security/2015/05/31/6
- http://www.ubuntu.com/usn/USN-2650-1
EPSS
CVE ID
Связанные уязвимости
The EAP-pwd peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not clear the L (Length) and M (More) flags before determining if a response should be fragmented, which allows remote attackers to cause a denial of service (crash) via a crafted message.
The EAP-pwd peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not clear the L (Length) and M (More) flags before determining if a response should be fragmented, which allows remote attackers to cause a denial of service (crash) via a crafted message.
The EAP-pwd peer implementation in hostapd and wpa_supplicant 1.0 through 2.4 does not clear the L (Length) and M (More) flags before determining if a response should be fragmented, which allows remote attackers to cause a denial of service (crash) via a crafted message.
The EAP-pwd peer implementation in hostapd and wpa_supplicant 1.0 thro ...
EPSS