On 15th Oct 2014, the OpenSSL project released version 1.0.1j that addressed [several security vulnerabilities](http://www.openssl.org/news/secadv_20141015.txt) of high severity or less. Official OpenVPN Windows installers bundle OpenSSL 1.0.1, necessitating a [new Windows installer release (I004/I604)](http://openvpn.net/index.php/download/community-downloads.html) by the OpenVPN project. On *NIX-based operating systems, OpenSSL is typically dynamically linked to OpenVPN, and the OS provider manages OpenSSL upgrades.
+
On 15th Oct 2014 the OpenSSL project released 1.0.1j that fixed [several security vulnerabilities](http://www.openssl.org/news/secadv_20141015.txt) of high severity or less. Official OpenVPN Windows installers bundle OpenSSL 1.0.1, which meant that the OpenVPN project had to make a [new Windows installer release](http://openvpn.net/index.php/download/community-downloads.html) (I004/I604). On *NIX-based operating systems OpenSSL is typically dynamically linked to OpenVPN and the OS provider handles the OpenSSL upgrades.
|SRTP Memory Leak|CVE-2014-3513|Denial-of-service only|TLS auth can[1] protect against this vulnerability|
+
|Session Ticket Memory Leak|CVE-2014-3567|Denial-of-service only|TLS auth can[1] protect against this vulnerability|
+
|SSL 3.0 Fallback protection|CVE-2014-3568|No SSLv3 in OpenVPN, not affected|
+
|Build option no-ssl3 is incomplete|-|No SSLv3 in OpenVPN, not affected|
Analysis of the impact of these vulnerabilities is taken from [here](http://thread.gmane.org/gmane.network.openvpn.devel/9133/focus=9139).
-
[^1]: The amount of protection is limited in environments where the TLS auth key is widely distributed (large organizations) or public (VPN service providers).
\
No newline at end of file
+
[1] The amount of protection is limited in environments where the TLS auth key is widely distributed (large organizations) or public (VPN service providers).
