list-openvpn-nl

list-openvpn-nl@lists.fox-it.com

37 discussions

Security advisory - upstream audits, remote DoS
by Steffan Karger 11 May '17

11 May '17

Summary: Upstream OpenVPN has been audited. The audits identified two remote DoS vulnerabilities. OpenVPN-NL is _not_ vulnerable to the pre-authentication DoS attack (CVE-2017-7478), but _is_ vulnerable to the very inefficient authenticated remote DoS attack (CVE-2017-7479). Due to the extremely limited nature of CVE-2017-7479, we will not release an OpenVPN-NL 2.3.x update, but instead continue our focus on making a 2.4.x release that contains these fixes. Background: Upstream OpenVPN 2.4 was simultaneously reviewed by Quarkslab (funded by OSTIF) and Cryptography Engineering LCC (funded by Private Internet Access) [0]. These audits both concluded that OpenVPN is a strong product, offering good security to it's users. Also, both audit praised the efforts of OpenVPN-NL in hardening both OpenVPN and OpenVPN-NL. The Quarkslab audit identified two remote Denial-of-Service vulnerabilities: 1) A pre-authentication Denial of Service (CVE-2017-7478) This affects OpenVPN 2.3.12 and newer. The most recent OpenVPN-NL is based on OpenVPN 2.3.9, and therefore _not_ vulnerable. Please refer to the upstream security announcement [0] for more information. 2) An authenticated Denial of Service (CVE-2017-7479) A fully authenticated client can cause the server's the packet-id counter to roll over, which would lead the server process to hit an ASSERT() and stop running. To make the server hit the ASSERT(), the client must first cause the server to send it 2^32 packets (at least 196GB). This makes it a _very_ inefficient DoS attack. Due to the extremely limited nature of CVE-2017-7479, we will not release an OpenVPN-NL 2.3.x update, but instead continue our focus on making a 2.4.x release that contains these fixes. Please refer to the upstream security announcement [0] for more information. [0] https://community.openvpn.net/openvpn/wiki/QuarkslabAndCryptographyEngineer…

1 0

OpenVPN-NL 2.3.9-nl2 released
by Steffan Karger 11 May '16

11 May '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A new version of OpenVPN-NL (2.3.9-nl2) is available on the OpenVPN-NL website [1]. This version is based on OpenVPN 2.3.9 [2], and PolarSSL 1.2.19 [3]. This new version of OpenVPN-NL includes fixes for a number of minor security issues in both OpenVPN [2] and PolarSSL [4,5,6]. If the recommended tls-auth mechanism is used in an OpenVPN-NL configuration, an attacker must possess the tls-auth key to mount an attack based on these issues. One issue is not stopped by tls-auth: a denial-of-service attack could be mounted when the --port-share option is enabled (which is disabled by default). In upstream OpenVPN and OpenVPN-NL before 2.3.8-nl1 this issue can cause a heap overflow, but OpenVPN-NL 2.3.8-nl1 already contains a hardening patch that limits this to denial-of-service. Users are advised to upgrade both OpenVPN-NL clients and servers to 2.3.9-nl2. References - ---------- [1] https://openvpn.fox-it.com/ [2] https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23 [3] https://tls.mbed.org/tech-updates/releases/mbedtls-2.2.1-2.1.4-1.3.16-and-p… [4] https://tls.mbed.org/tech-updates/releases/mbedtls-2.2.0-2.1.3-1.3.15-and-p… [5] https://tls.mbed.org/tech-updates/releases/mbedtls-2.1.2-and-1.3.14-and-pol… [6] https://tls.mbed.org/tech-updates/releases/mbedtls-2.1.1-and-1.3.13-and-pol… -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXMzxiAAoJEEEwndWOY1w5TmcH/0F/G+frzd66SikvVe9VWupQ WyBswExUGD7wfRphluzOsvs2a+cawWJmJrsBEORz5oTHt95TFRfZgWzHKXrjW5yM py0sc3boV6Sxqkb5WiJc5+bnEa6DOQ5OouFzw22L3Q2rEmyq8T1eBUpKbt+1XDTc cgqGOnrlEi7WW1Ii3rgG5cbGk8wRzld8/ZgxkDWXUOkOVw+pVMrXCXFKqkLlMZIi MGuBMuP7veATlZ5j0p66VqGqBUmBnki523GiSqLdYz0nhS8i7weyfhIobax4HPnW ivi5Cq2O/4IkBJLqLCsBnsylAVOtM2YBy8HcJPtZanjxkfxjx3vfQGit+7CON2Y= =Geon -----END PGP SIGNATURE-----

1 0

Security advisory - SLOTH
by Steffan Karger 18 Jan '16

18 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Summary: OpenVPN-NL is not vulnerable to the SLOTH attack [0]. Background: On January 6th 2016, INRIA published information on a TLS vulnerability called 'SLOTH' [0]. The vulnerability allows an attacker to impersonate a client with client certificate if the following conditions are met: * the attacker has a Man-in-the-Middle position between a client and server, * the client is willing to authenticate itself with its certificate to the MitM attacker, * both parties support TLS 1.2, and, * both parties allow MD5 ciphersuites to be used. OpenVPN-NL does not allow MD5 cipher suites, and therefore is not vulnerable to the SLOTH attack. [0] http://www.mitls.org/pages/attacks/SLOTH -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWnKu2AAoJEEEwndWOY1w5GsAIAIteWS56EKrVnBAi05gq0W1u nXBpta4Wm/rCHIxiWKViKWoKameHksfS3aLLiaO/qxOj9AwhsKzln5IiGNfJpE97 TaZFZb1JOddVckBzMsIphBLttctDeb7bW6cwQgF8Vn0wl+MYekHSRGtTXxAQZqiX SSYXTVjqbqsmg03V3jQQ8yiFF82N7eMRQ/jxitrKz7PosCPSbCSIVSY95rijbgLB h/sZ7LLCSUtpg82ZIVHs35LNFKFGZeCHnzjNpeVpGNxYdi6GrfROJL21qJ/QjXKm k1R+OoDHXIN204aLbpkbVZRQKSCI2is5y3J+K7RZtVOnxyW7eD09BSRI/AaCMH4= =hvWX -----END PGP SIGNATURE-----

1 0

OpenVPN-NL 2.3.8-nl1 released
by Steffan Karger 21 Aug '15

21 Aug '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A new version of OpenVPN-NL (2.3.8-nl1) is available on the OpenVPN-NL site [1]. This version is based on OpenVPN 2.3.8 [2], and PolarSSL 1.2.15 [3]. This new version of OpenVPN-NL includes fixes for a number of minor security issues in PolarSSL [4][5]. If the recommended tls-auth mechanism is used in an OpenVPN-NL configuration, an attacker can only use these to attack such an OpenVPN-NL instance if (s)he is in possession of the tls-auth key. Users are advised to upgrade both OpenVPN-NL clients and servers to 2.3.8-nl1. Important: with this release, the code signing keys have changed, to move to SHA256 instead of SHA1 signature digests. The old keys are _not_ compromised. We now use keys with the following fingerprints to sign OpenVPN-NL releases: Linux: 6A11 9596 8DDC A349 4E7C 598C 43CF 15D3 54E0 3E30 Windows: 0456 cab6 4107 209a 470d 4439 09c5 cee5 576f 9000 Debian/Ubuntu users should import the new keys by: wget https://openvpn.fox-it.com/repos/fox-crypto-gpg.asc gpg --with-fingerprint fox-crypto-gpg.asc # (verify fingerprint) sudo apt-key add fox-crypto-gpg.asc Red Hat / SuSE users should import new keys by: wget https://openvpn.fox-it.com/repos/fox-crypto-gpg.asc gpg --with-fingerprint fox-crypto-gpg.asc # (verify fingerprint) sudo rpm --import fox-crypto-gpg.asc Windows users should verify the key fingerprint through properties->digital signatures before starting the installer. References - ---------- [1] https://openvpn.fox-it.com/ [2] https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23 [3] https://tls.mbed.org/tech-updates/releases/polarssl-1.2.15-released [4] https://tls.mbed.org/tech-updates/releases/polarssl-1.2.14-released [5] https://tls.mbed.org/tech-updates/releases/polarssl-1.2.13-released -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV1yq+AAoJEEEwndWOY1w5FTUH/2YaJi4RsdUve3536/G1qraQ Q/Fu0J1YLkvnJp/pP8kwiLNj2XCNFiu+F6CqfCyOoUXyIIn3CtSfHhS6TiYctuj0 TtlWXPMeA051AaCPq4YNaen6xLB/j9vRpFPge3rmgWoJ3LcpqRvLhSSfnr9PhYnZ t2tXAb/QlUQ7wdjOV3aIKl1OWaxIYSz75lw1PHv4aaV+kygM8+a4NsxCKE8vb4O9 Cmy/HQhwZLF57P6BIfB5SCw8mhLygmfezaTj91kcl64drLD8c/6YN+KUiG4Ee8kO laUtyXQilpCJdBedcAuXDNdMbZOIAOqopphx8ooVxSVSwB11Kn4nMuNM/IoIdx4= =v2Mm -----END PGP SIGNATURE-----

1 0

Security advisory: Logjam / weakdh
by Steffan Karger 20 May '15

20 May '15

Summary: OpenVPN-NL is not vulnerable to the Logjam attack [logjam] and no action is required from OpenVPN-NL administrators or users. Full description: Critical vulnerabilities in Diffie-Hellman key-exchanges and the TLS protocol, dubbed 'Logjam', have been published this morning [logjam]. The authors of [logjam] show a man-in-the-middle attack on TLS that downgrades the DH parameters used for key-exchange to EXPORT-grade (512-bits) parameters, if both client and server have support for export-grade parameters. Furthermore, the authors show they can break 512-bits DH key exchanges, based on a known DH group, within 90 seconds. They argue the scientific community should be able to break 768-bits parameters and state actors might be able to break 1024-bits parameters. OpenVPN-NL is not vulnerable to Logjam for the following reasons: 1) OpenVPN encourages users to generate their own DH-parameters, rather than using a known DH-group. 2) OpenVPN-NL enforces the use of 2048-bit DH parameters, which is considered large enough to be infeasible to break. 3) OpenVPN-NL can not be configured to support export-grade DH parameters. Furthermore, use of the recommended tls-auth feature would block the man-in-the-middle downgrade attack. [logjam] https://weakdh.org/

1 0

OpenVPN-NL v2.3.5-nl3 released
by Steffan Karger 19 Jan '15

19 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A new version of OpenVPN-NL (2.3.5-nl3) is available on the OpenVPN-NL site [1]. This version is based on OpenVPN 2.3.5 [2], and PolarSSL 1.2.12 [3]. This new version of OpenVPN-NL fixes a potential double free vulnerability in PolarSSL [4]. The vulnerability enables an attacker that can send TLS messages to an OpenVPN-NL instance to trick that instance to free an uninitialized pointer. This enables an attacker to mount a denial of service attack, and could potentially lead to remote code execution. If the recommended tls-auth mechanism is used in an OpenVPN-NL configuration, an attacker can only attack such an OpenVPN-NL instance if (s)he is in possession of the tls-auth key. We have not (yet) seen any exploits targeting this vulnerability. Users are advised to upgrade both OpenVPN-NL clients and servers to 2.3.5-nl3. References - ---------- [1] https://openvpn.fox-it.com/ [2] https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23 [3] https://polarssl.org/tech-updates/releases/polarssl-1.2.12-released [4] https://polarssl.org/tech-updates/security-advisories/polarssl-security-adv… -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJUvSPCAAoJEEEwndWOY1w59Y4H/jQP2fqvCDzLc5D0syd650tP sqo6jW2WLxvLTF0bPKYyyy3A1V2Uu+SKjAwcCmA2+UbFjpFlHW28yFeaMclgrHrm 9DWKIXfSaCgal6VWYTuzFmz+z3KhmCLnOBfjHehDw2bPsfFkbb+ILbZbZ2MLowud jlnPISOwwuQdeXZTRJRScGhO6iY87DR4QpMnIRYtFsnqKoW4jEF1Ij4naELS8Mxf jSJZU87/MQsCM3gSAUfAtfV8KFV/AA6nVRg9b459oyOan4eQ2IaYpFZZrIP1Cmy6 U2C8aq4LsIz+WaIIJBoyVqYPeFH6vzWW2me+3heSOIRANWNWHMSoJ/VCH6t2uBI= =kBi3 -----END PGP SIGNATURE-----

1 0

OpenVPN-NL v2.3.5-nl2 released
by Steffan Karger 01 Dec '14

01 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A new version of OpenVPN-NL (2.3.5-nl2) is available on the OpenVPN-NL site [1]. This version is based on OpenVPN 2.3.5 [2], and PolarSSL 1.2.12 [3]. This new version of OpenVPN-NL fixes a denial-of-service vulnerability [4]. The vulnerability enables authenticated clients to stop openvpn server instances, potentially causing availability issues. Confidentiality and authenticity of traffic are *not* affected. OpenVPN-NL server administrators are recommended to upgrade their server instances to 2.3.5-nl2 as soon as possible. OpenVPN-NL client instances are not directly affected, and can be updated according to your regular update schedule. References - ---------- [1] https://openvpn.fox-it.com/ [2] https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23 [3] https://polarssl.org/tech-updates/releases/polarssl-1.2.12-released [4] https://community.openvpn.net/openvpn/wiki/SecurityAnnouncement-97597e732b -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJUfLNHAAoJEEEwndWOY1w5SogH/RQv29CDaBylVJYwaL27UfGh baThd6/li1Nm2J4zIXeMfPUL8QJN1HYl3XWbtcyB991pjkaMV4kxvvckj5rJVxHx uYQO4biytbvAKAJVtcaQKfN4LWMNZCDmNKuDahRXIlgdb1Ogpq7D95XziGjTN3m6 61VrxekUKeGQq5YDN8za+Jx8KnxxDqOmyDFuxTXNdOkPE0ZpBfdZ5/7VPxIQTOTD qI6je0gH8lXSS6E+Vvm4VglbxcG/0Ak5hD0Ynhtm5hh7c8FHEpLOWZcs39Yp54lg aKdrFxOArley6edFgLSuDkHFH3W8uV/CVaIerflBYRfkoGYN7SsEl15CDCaiHNc= =sTCd -----END PGP SIGNATURE-----

1 0

Pre-notification: upcoming release
by Steffan Karger 01 Dec '14

01 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A denial of service security vulnerability affecting OpenVPN-NL servers was recently brought to our attention. The vulnerability enables authenticated clients to stop openvpn server instances. The vulnerability affects server availability only. Confidentiality and authenticity of traffic are *not* affected. A fixed version of OpenVPN-NL will be released today (1st Dec 2014) at around 18:00 UTC (20:00 CET). Upstream (regular OpenVPN) will also release a fixed version around the same time. More details will be released to the public once the fixed versions are available. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJUfCMFAAoJEEEwndWOY1w5yQAH/3o7+r1qd7CWpiP4ibizGqBd 53RST7V8Y6B0ivieFKVeGIdYLp3GqVTXmFStVSmSsY3kBPMxMfDmLlwkRaCTK+OH Oft9r4VLCwSUvPLMW/bppxiDXb96sltUe87fl6hHhkHWSUYJy/yh4C/bEEModCv9 BvsYqVT/tCeREb0DJKyFLNJ8jEK2AfmAd3ccNBV41M30JJs2MQ01PtjoMdeCVMRZ bXRjcomilTsVGmLYnfDhAqCc9g184aDphxE5qgFwrfVOJc38P7lhB2jZdfq0GgzS rOKSfkNkoWg/ejMijja2n8RLGw/QSIEYqfXpUY4fqR5efXwgPTRKYf9/ijYMVqk= =6QO5 -----END PGP SIGNATURE-----

1 0

OpenVPN-NL v2.3.5-nl1 released
by Steffan Karger 17 Nov '14

17 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 A new version of OpenVPN-NL (2.3.5-nl1) is available on the OpenVPN-NL site [1]. This version is based on OpenVPN 2.3.5 [2], and PolarSSL 1.2.12 [3]. This new version of OpenVPN-NL includes a new PolarSSL release, which fixes a remotely-triggerable memory leak when parsing some X.509 certificates. When using tls-auth, this can only be achieved when the group key ("tls-auth") has been compromised. A successful attack can potentially cause a denial-of-service; confidentiality and authenticity are not compromised. This release contains some minor bugfixes in both PolarSSL and OpenVPN [2,3]. References - ---------- [1] https://openvpn.fox-it.com/ [2] https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23 [3] https://polarssl.org/tech-updates/releases/polarssl-1.2.12-released -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJUaby3AAoJEEEwndWOY1w5kH4H/3/tkhQ0Zus3b23JRqG0fyzF mXB49uLsMWoc08J35TU4akCPgg+fLnirW8petCKEHztcshklbfpC8TmRyr5FPrWQ hcDTVSaDZs6Ey5KdXnVd69pcBGaGL4lwRNNL3T/pMXVjh73zkS6QCncVkwkyY/Pc oI9x4D8UkZbK+nf3hwevcF15MYLvkcBfmsa3UfdrSujgDV8l/5zi/RW6EPAh5oLx Seh5FubuMrk+oD2ECw075Itg5b+SYTXPO9Wkk/C++db0rBR4o6uq5YiguSONNmjo FaB9HcnbG8sf4KduvwxH0tZV+X1DzWAnJdz/Xudn7rHUR114bJ46xYuKSO1Uqps= =B9jG -----END PGP SIGNATURE-----

1 0

Security advisory - POODLE
by Steffan Karger 15 Oct '14

15 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Summary: OpenVPN-NL is not vulnerable to the POODLE attack on SSLv3 [1]. Background: On October 14th 2014, Google released a SSLv3 vulnerability called 'POODLE' [1]. The vulnerability allows an attacker to obtain the plaintext of connections secured with SSLv3. OpenVPN-NL is not vulnerable, since OpenVPN-NL never supported SSLv3 or SSLv3 fallback. [1] http://googleonlinesecurity.blogspot.nl/2014/10/this-poodle-bites-exploitin… -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJUPjjkAAoJEEEwndWOY1w5CIIH/2vFFL4eCqRn2U6MqPNSUWis nMMFJpjsKWXc2ItGEGJwYCrPqpGJfJ47NVAfQRO3q+hXg7sgaj7MT+Phyv4+id7Z 535GIMLCXP9WCliUJFYac7665XdfwrmzNcFTFuqrqtfVwBsajMuECasExga/ubuV GjZ/7cNYOhtfzQcS4JnqcDbWERwqzky0RvkDnaVVFWQqKyuceJBzdIML+iY46+d2 0eAhdn58VZb8LZqYEPZYD/AnRGbR7R1SgGQ58wRMz07fcYyA8x4YxbAzaHztO9Yf 2nuifBGxk/3TX0WKDIQcNbP56gUcAuilfHW7JriqbiAMV6ya5b8lPpGBUbm3xh8= =pSYZ -----END PGP SIGNATURE-----

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

list-openvpn-nl