Sicherheit: Mehrere Probleme in OpenVPN
||Mehrere Probleme in OpenVPN
||SUSE openSUSE Leap 42.2
||Mo, 26. Juni 2017, 16:48
openSUSE Security Update: Security update for openvpn
Announcement ID: openSUSE-SU-2017:1680-1
Cross-References: CVE-2017-7508 CVE-2017-7520 CVE-2017-7521
openSUSE Leap 42.2
An update that fixes three vulnerabilities is now available.
This update for openvpn fixes the following issues:
- Some parts of the certificate-parsing code did not always clear all
allocated memory. This would have allowed clients to leak a few bytes of
memory for each connection attempt, thereby facilitating a (quite
inefficient) DoS attack on the server. [bsc#1044947, CVE-2017-7521]
- The ASN1 parsing code contained a bug that could have resulted in some
buffers being free()d twice, and this issue could have potentially been
triggered remotely by a VPN peer. [bsc#1044947, CVE-2017-7521]
- If clients used a HTTP proxy with NTLM authentication, a
man-in-the-middle attacker between client and proxy could cause the
client to crash or disclose at most 96 bytes of stack memory. The
disclosed stack memory was likely to contain the proxy password. If the
proxy password had not been reused, this was unlikely to compromise the
security of the OpenVPN tunnel itself. Clients who did not use the
--http-proxy option with ntlm2 authentication were not affected.
- It was possible to trigger an assertion by sending a malformed IPv6
packet. That issue could have been abused to remotely shutdown an
openvpn server or client, if IPv6 and --mssfix were enabled and if the
IPv6 networks used inside the VPN were known. [bsc#1044947,
This update was imported from the SUSE:SLE-12:Update update project.
To install this openSUSE Security Update use YaST online_update.
Alternatively you can run the command listed for your product:
- openSUSE Leap 42.2:
zypper in -t patch openSUSE-2017-730=1
To bring your system up-to-date, use "zypper patch".
- openSUSE Leap 42.2 (i586 x86_64):
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org