Question
How To Fix CVE-2016-2107 on Ubuntu 14.04?
- Posted on July 19, 2016
- Let's EncryptNginxSecurityDigitalOceanNode.jsUbuntu
Asked by itsupport729928
Hello Digital Ocean Community -
For reference my setup is Ubuntu 14.04 with nginx
I need your help! I followed this guide (https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-14-04) to set up KingsKidsClub.com and SacramentoKingsKidsClub.com.
Installation went well except for testing the security on ssllabs at the end of step 3. See: https://www.ssllabs.com/ssltest/analyze.html?d=kingskidsclub.com https://www.ssllabs.com/ssltest/analyze.html?d=sacramentokingskidsclub.com
I failed both tests, apparently I have a vulnerability called: “CVE-2016-2107”
So far I’ve tried the following without luck:
https://gist.github.com/ArturT/bc8836d3bedff801dc324ac959050d12
Anyone know how I can fix this issue? Thank you in advance for any help!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hi!
The Ubuntu package maintainers have already pushed patched packages that should fix the vulnerability. Run the following command to upgrade the OpenSSL libraries on your system which Nginx uses:
You will need to restart Nginx in order for the changes to take effect:
Per the bobcares article that you linked, you can make sure that you got the right packages by checking if the vulnerability is mentioned in the changelog:
you can also check your fix here: https://filippo.io/CVE-2016-2107
This comment has been deleted