Описание
The server implementation of the EAP-MSCHAPv2 protocol in the eap-mschapv2 plugin in strongSwan 4.2.12 through 5.x before 5.3.4 does not properly validate local state, which allows remote attackers to bypass authentication via an empty Success message in response to an initial Challenge message.
The server implementation of the EAP-MSCHAPv2 protocol in the eap-mschapv2 plugin in strongSwan 4.2.12 through 5.x before 5.3.4 does not properly validate local state, which allows remote attackers to bypass authentication via an empty Success message in response to an initial Challenge message.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2015-8023
- https://www.strongswan.org/blog/2015/11/16/strongswan-vulnerability-%28cve-2015-8023%29.html
- https://www.strongswan.org/blog/2015/11/16/strongswan-vulnerability-(cve-2015-8023).html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00025.html
- http://lists.opensuse.org/opensuse-updates/2015-11/msg00139.html
- http://www.debian.org/security/2015/dsa-3398
- http://www.securityfocus.com/bid/84947
- http://www.ubuntu.com/usn/USN-2811-1
Связанные уязвимости
The server implementation of the EAP-MSCHAPv2 protocol in the eap-mschapv2 plugin in strongSwan 4.2.12 through 5.x before 5.3.4 does not properly validate local state, which allows remote attackers to bypass authentication via an empty Success message in response to an initial Challenge message.
The server implementation of the EAP-MSCHAPv2 protocol in the eap-mschapv2 plugin in strongSwan 4.2.12 through 5.x before 5.3.4 does not properly validate local state, which allows remote attackers to bypass authentication via an empty Success message in response to an initial Challenge message.
The server implementation of the EAP-MSCHAPv2 protocol in the eap-mschapv2 plugin in strongSwan 4.2.12 through 5.x before 5.3.4 does not properly validate local state, which allows remote attackers to bypass authentication via an empty Success message in response to an initial Challenge message.
The server implementation of the EAP-MSCHAPv2 protocol in the eap-msch ...
