How to fix 'logjam' vulnerability in Apache (httpd)
From the article you linked, there are three recommended steps to protect yourself against this vulnerability. In principle these steps apply to any software you may use with SSL/TLS but here we will deal with the specific steps to apply them to Apache (httpd) since that is the software in question.
- Disable Export Cipher Suites
Dealt with in the configuration changes we'll make in 2. below (
!EXPORT near the end of the
SSLCipherSuite line is how we'll disable export cipher suites)
- Deploy (Ephemeral) Elliptic-Curve Diffie-Hellman (ECDHE)
For this, you need to edit a few settings in your Apache config files - namely
SSLHonorCipherOrder to have a "best-practices" setup. Something like the following will suffice:
SSLProtocol all -SSLv2 -SSLv3 SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA SSLHonorCipherOrder on
Note: as for which
SSLCipherSuite setting to use, this is always changing, and it is a good idea to consult resources such as this one to check for the latest recommended configuration.
3. Generate a Strong, Unique Diffie Hellman Group
To do so, you can run
openssl dhparam -out dhparams.pem 2048.
Note that this will put significant load on the server whilst the params are generated - you can always get around this potential issue by generating the params on another machine and using
scp or similar to transfer them onto the server in question for use.
To use these newly-generated
dhparams in Apache, from the Apache Documentation:
To generate custom DH parameters, use the openssl dhparam command. Alternatively, you can append the following standard 1024-bit DH parameters from RFC 2409, section 6.2 to the respective SSLCertificateFile file:
which is then followed by a standard 1024-bit DH parameter. From this we can infer that the custom-generated DH parameters may simply be appended to the relevant
SSLCertificateFile in question.
To do so, run something similar to the following:
cat /path/to/custom/dhparam >> /path/to/sslcertfile
Alternatively, as per the Apache subsection of the article you originally linked, you may also specify the custom dhparams file you have created if you prefer not to alter the certificate file itself, thusly:
SSLOpenSSLConfCmd DHParameters "/path/to/dhparams.pem"
in whichever Apache config(s) are relevant to your particular SSL/TLS implementation - generally in
conf.d/vhosts.conf but this will differ depending on how you have configured Apache.
It is worth noting that, as per this link,
Before Apache 2.4.7, the DH parameter is always set to 1024 bits and is not user configurable. This has been fixed in mod_ssl 2.4.7 that Red Hat has backported into their RHEL 6 Apache 2.2 distribution with httpd-2.2.15-32.el6
On Debian Wheezy upgrade apache2 to 2.2.22-13+deb7u4 or later and openssl to 1.0.1e-2+deb7u17. The above SSLCipherSuite does not work perfectly, instead use the following as per this blog:
You should check whether your Apache version is later than these version numbers depending on your distribution, and if not - update it if at all possible.
Once you have performed the above steps to update your configuration, and restarted the Apache service to apply the changes, you should check that the configuration is as-desired by running the tests on SSLLabs and on the article related to this particular vulnerability.