How to fix CVE-2015-4000 LOGJAM TLS DH vulnerability?

A CVE-2015-4000 vulnerability in the TLS protocol implementation, so-called "Logjam". "Logjam" is an attack against the Diffie-Hellman key-exchange protocol used in TLS.

There are two issues referred by word"Logjam":

1. Logjam attack against the TLS protocol.
   The Logjam attack allows a man-in-the-middle attacker to downgrade vulnerable TLS connections to 512-bit export-grade cryptography. This allows the attacker to read and modify any data passed over the connection. The attack is reminiscent of the FREAK attack , but is due to a flaw in the TLS protocol rather than an implementation vulnerability, and attacks a Diffie-Hellman key exchange rather than an RSA key exchange. The attack affects any server that supports DHE_EXPORT ciphers, and affects all modern web browsers. 8.4% of the Top 1 Million domains were initially vulnerable.

2. Weak Diffie-Hellman . (Threats from state-level adversaries.)

   Millions of HTTPS, SSH, and VPN servers all use the same prime numbers for Diffie-Hellman key exchange. Practitioners believed this was safe as long as new key exchange messages were generated for every connection. However, the first step in the number field sieve—the most efficient algorithm for breaking a Diffie-Hellman connection—is dependent only on this prime. After this first step, an attacker can quickly break individual connections.

   We carried out this computation against the most common 512-bit prime used for TLS and demonstrate that the Logjam attack can be used to downgrade connections to 80% of TLS servers supporting DHE_EXPORT . We further estimate that an academic team can break a 768-bit prime and that a nation-state can break a 1024-bit prime. Breaking the single, most common 1024-bit prime used by web servers would allow passive eavesdropping on connections to 18% of the Top 1 Million HTTPS domains. A second prime would allow passive decryption of connections to 66% of VPN servers and 26% of SSH servers. A close reading of published NSA leaks shows that the agency's attacks on VPNs are consistent with having achieved such a break.

   Here is a whitepaper which describes this vulnerability.

Since Plesk 12.5 there is a utility plesk sbin sslmng that allows disabling TLS compression and sets the DH parameter's size to 2048.

To do it for all services, do following:

1. Connect to server over SSH.

2. Run the following command:

   # plesk sbin sslmng -vvv --strong-dh --dhparams-size=2048

   Note: To change the setting for a particular service, option --services=service_name should be used.

Warning: Execution of the script below on the Plesk 12.5 and above can make Plesk inoperable due to duplicate ssl_ directives.

Warning: Apply the script on a test environment first. Contact Plesk Technical Support in case of any issues.

The script will patch properly if you have OpenSSL version 1.0.1 and higher, because earlier versions do not have TLS v1.1 and TLS v1.2 support.

Steps of the solution:

1. Connect to the server via SSH.
2. Download the script, unzip and run it:

   # wget https://support.plesk.com/hc/article_attachments/115004355285/SSLfix.zip
   # unzip SSLfix.zip
   # chmod +x SSLfix.sh
   # ./SSLfix.sh [v3|dh] [service name like apache, ngin

   Without arguments, it will patch all services' configuration for SSLv3 (Poodle) and weak DH (Logjam).

Operating system (OS) vendors released the following security advisories to address this vulnerability:

• Debian
• RedHat/CentOS
• Ubuntu

1. Connect to server over RDP.
2. Open the Group Policy Object Editor: type gpedit.msc in the Start > Run dialogue window.
3. Expand Computer Configuration > Administrative Templates > Network > SSL Configuration Settings.
4. Under SSL Configuration Settings , open the SSL Cipher Suite Order setting.
5. Set up a strong cipher suite order. See this list of Microsoft's supported ciphers and Mozilla's TLS configuration instructions.

How to achieve an A rating on Qualys SSL Labs with Windows