bugtraq - [SECURITY] [DSA 3398-1] strongswan security update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Mon, 16 Nov 2015 14:14:07 +0100
From: Yves-Alexis Perez <corsac@...ian.org>
To: bugtraq@...urityfocus.com
Subject: [SECURITY] [DSA 3398-1] strongswan security update

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- -------------------------------------------------------------------------
Debian Security Advisory DSA-3398-1                   security@...ian.org
https://www.debian.org/security/                        Yves-Alexis Perez
November 16, 2015                     https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : strongswan
CVE ID         : CVE-2015-8023

Tobias Brunner found an authentication bypass vulnerability in
strongSwan, an IKE/IPsec suite.

Due to insufficient validation of its local state the server
implementation of the EAP-MSCHAPv2 protocol in the eap-mschapv2 plugin
can be tricked into successfully concluding the authentication without
providing valid credentials.

It's possible to recognize such attacks by looking at the server logs.
The following log message would be seen during the client
authentication:

  EAP method EAP_MSCHAPV2 succeeded, no MSK established

For the oldstable distribution (wheezy), this problem has been fixed
in version 4.5.2-1.5+deb7u8.

For the stable distribution (jessie), this problem has been fixed in
version 5.2.1-6+deb8u2.

For the testing distribution (stretch), this problem has been fixed
in version 5.3.3-3.

For the unstable distribution (sid), this problem has been fixed in
version 5.3.3-3.

We recommend that you upgrade your strongswan packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@...ts.debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJWSdZXAAoJEG3bU/KmdcClzmwIAKSxdiqejnrNE0GrLBxiuG9h
dTn/aRw0OaOrXUs/Gmi7fMy0ce0ZqoTm5tExVAh9PsuRGqgxMfjuPQs+jt8XEAGf
ZW7PeRQoej5XgIiMpoMM+Z1jNjgY2aTgccqS1kGWvRXdWycMKTHEFFVk5vHopuqv
iR5+kVX0OxLn043Iu77EmpBYqxIbVG8acHEOCgIfef80rNPaDksvwqV3I7swnAWx
t0ezoNZglHTCfOefcj7RRgEpcPL/7UIv3CVBmtw60E6P+//jXE6fmhjkf6B5BEjx
QZAMUiEqRtkjXil8xdDoJTVHJQ9UKXSGrTimZyrF7M0+JlpUvNzeB5ynaMh+OtQ=
=8xMJ
-----END PGP SIGNATURE-----