This issue depends on the webserver configuration. Depending on the web server you use, you should configure it so that it uses an appropriate modern cipher and protocol version.
A word of warning: take the time to read and document yourself on each specific configuration, do not blindly copy and paste them as they can affect your current and future setup for the site and how users will connect to your site.
Even if, for your own words, I’m a web developer and i don’t have a large knowledge in system configuration, this is not the kind of question where you can get a “copy-paste” solution.
This is really off topic but... keep in mind that the fact that your Linux distribution is using a specific version doesn't mean that this version is not being patched to solve CVE vulnerabilities.
Just an example, in the link you posted to apache CVE vulnerabilities, the last CVE (mod_lua: Crash in websockets PING handling CVE-2015-0228) has been solved in official apache 2.4.16 but Debian stable (jessie) is using apache 2.4.10, but that doesn't mean that it is vulnerable because this version is being pacthed to solve this kind of issues. Following this apache example, debian fixed it in version 2.4.10-10+deb8u4 CVE-2015-0228
Reading your comment seems like the op should raise their arms and start to run in circles
Anyway, it's worth your advice to keep the system updated.
See also https://mozilla.github.io/server-side-tls/ssl-config-generator/
You put in there your server type and version, openssl version and what kind of configuration you prefer (i.e.: do you need to support IE6/XP?) and the site give you a recommended configuration.
You need to modify some files under /etc/apache2/ and then reload or restart apache, but please read the documentation until you fully understand what you are doing.
For example if you enable HSTS by mistake and them disable it many people won’t be able to access your website anymore.