How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

365,542

Total vulnerabilities in the database

Vulnerabilities for products matching "http_server"

Found 15 matching products. Filters apply to all results.

You can search for specific versions with /product/http_server/1.2.3

apache / http_server

1978 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2019-10097	High	September 26, 2019 9/26/19	== 2.4.33 == 2.4.37 == 2.4.38 == 2.4.34 == 2.4.35
CVE-2019-10098	Medium	September 25, 2019 9/25/19	>= 2.4.0 <= 2.4.39
CVE-2019-10081	Medium	August 15, 2019 8/15/19	>= 2.4.20 <= 2.4.39
CVE-2019-9517	High	August 13, 2019 8/13/19	>= 2.4.20 < 2.4.40
CVE-2019-0197	Low	June 11, 2019 6/11/19	>= 2.4.34 <= 2.4.38
CVE-2019-0196	Medium	June 11, 2019 6/11/19	>= 2.4.17 <= 2.4.38
CVE-2019-0220	Medium	June 11, 2019 6/11/19	>= 2.4.0 <= 2.4.38
CVE-2019-0211	High	April 8, 2019 4/8/19	>= 2.4.17 <= 2.4.38
CVE-2019-0217	High	April 8, 2019 4/8/19	>= 2.4.0 <= 2.4.38
CVE-2019-0215	Medium	April 8, 2019 4/8/19	== 2.4.37 == 2.4.38
CVE-2018-17189	Medium	January 30, 2019 1/30/19	== 2.4.20 == 2.4.23 == 2.4.25 == 2.4.26 == 2.4.18 == 2.4.17 == 2.4.27 == 2.4.29 == 2.4.28 == 2.4.33 == 2.4.37 == 2.4.30 == 2.4.34 == 2.4.35
CVE-2018-17199	Medium	January 30, 2019 1/30/19	>= 2.4.0 <= 2.4.37
CVE-2019-0190	High	January 30, 2019 1/30/19	== 2.4.37
CVE-2018-11763	Low	September 25, 2018 9/25/18	>= 2.4.17 <= 2.4.34
CVE-2016-4975	Low	August 14, 2018 8/14/18	== 2.2.23 == 2.4.1 == 2.4.20 == 2.2.11 == 2.2.0 == 2.2.31 == 2.2.10 == 2.4.6 == 2.2.13 == 2.2.2 == 2.4.12 == 2.2.4 == 2.2.17 == 2.2.16 == 2.2.21 == 2.4.3 == 2.4.23 == 2.2.8 == 2.4.4 == 2.4.10 == 2.4.7 == 2.2.14 == 2.2.24 == 2.2.25 == 2.2.6 == 2.2.22 == 2.2.19 == 2.2.27 == 2.2.9 == 2.4.18 == 2.2.18 == 2.2.12 == 2.2.29 == 2.2.3 == 2.4.2 == 2.2.15 == 2.2.20 == 2.4.17 == 2.4.16 == 2.4.9 == 2.2.26
CVE-2017-12171	Medium	July 26, 2018 7/26/18	== 2.2.15-60
CVE-2018-8011	Medium	July 18, 2018 7/18/18	== 2.4.33
CVE-2018-1333	Medium	June 18, 2018 6/18/18	== 2.4.33 >= 2.4.18 <= 2.4.30
CVE-2017-15710	Medium	March 26, 2018 3/26/18	== 2.4.1 == 2.4.20 == 2.4.6 == 2.4.12 == 2.4.3 == 2.4.23 == 2.4.4 == 2.4.10 == 2.4.7 == 2.4.25 == 2.4.26 == 2.4.18 == 2.4.2 == 2.4.17 == 2.4.16 == 2.4.9 == 2.4.27 == 2.4.29 == 2.4.28
CVE-2017-15715	Medium	March 26, 2018 3/26/18	>= 2.4.0 <= 2.4.29
CVE-2018-1283	Low	March 26, 2018 3/26/18	>= 2.4.0 <= 2.4.29
CVE-2018-1301	Low	March 26, 2018 3/26/18	<= 2.4.29
CVE-2018-1302	Low	March 26, 2018 3/26/18	<= 2.4.29
CVE-2018-1303	Medium	March 26, 2018 3/26/18	<= 2.4.29
CVE-2018-1312	Critical	March 26, 2018 3/26/18	== 2.4.1 == 2.4.20 == 2.4.6 == 2.4.12 == 2.4.3 == 2.4.23 == 2.4.4 == 2.4.10 == 2.4.7 == 2.4.25 == 2.4.26 == 2.4.18 == 2.4.2 == 2.4.17 == 2.4.16 == 2.4.9 == 2.4.27 == 2.4.29 == 2.4.28
CVE-2016-8612	Low	March 9, 2018 3/9/18	< 2.4.23
CVE-2017-9798	High	September 18, 2017 9/18/17	== 2.4.1 == 2.4.20 == 2.4.6 == 2.4.0 == 2.4.12 == 2.4.3 == 2.4.23 == 2.4.4 == 2.4.10 == 2.4.7 == 2.4.25 == 2.4.26 == 2.4.18 == 2.4.2 == 2.4.17 == 2.4.16 == 2.4.9 == 2.4.27 <= 2.2.34
CVE-2016-0736	Medium	July 27, 2017 7/27/17	== 2.4.1 == 2.4.20 == 2.4.6 == 2.4.0 == 2.4.12 == 2.4.3 == 2.4.23 == 2.4.8 == 2.4.10 == 2.4.7 == 2.4.14 == 2.4.22 == 2.4.2 == 2.4.19 == 2.4.16 == 2.4.9 == 2.4.21
CVE-2016-2161	Medium	July 27, 2017 7/27/17	== 2.4.1 == 2.4.20 == 2.4.6 == 2.4.0 == 2.4.12 == 2.4.3 == 2.4.23 == 2.4.8 == 2.4.10 == 2.4.7 == 2.4.14 == 2.4.22 == 2.4.2 == 2.4.19 == 2.4.16 == 2.4.9 == 2.4.21
CVE-2016-8743	High	July 27, 2017 7/27/17	>= 2.4.1 <= 2.4.23 >= 2.2.0 <= 2.2.31
CVE-2017-7659	Medium	July 26, 2017 7/26/17	== 2.4.25 == 2.4.24
CVE-2017-9788	Medium	July 13, 2017 7/13/17	<= 2.2.33 >= 2.4.0 <= 2.4.26
CVE-2017-9789	Medium	July 13, 2017 7/13/17	== 2.4.26
CVE-2017-3167	Critical	June 20, 2017 6/20/17	>= 2.2.0 < 2.2.33 >= 2.4.0 < 2.4.26
CVE-2017-3169	High	June 20, 2017 6/20/17	== 2.2.23 == 2.4.1 == 2.4.20 == 2.2.11 == 2.2.0 == 2.2.31 == 2.2.13 == 2.2.2 == 2.4.12 == 2.2.17 == 2.2.16 == 2.2.21 == 2.4.23 == 2.4.10 == 2.2.14 == 2.2.24 == 2.2.25 == 2.2.30 == 2.2.22 == 2.2.19 == 2.2.27 == 2.4.25 == 2.4.18 == 2.2.18 == 2.2.12 == 2.2.32 == 2.2.29 == 2.2.3 == 2.4.2 == 2.2.15 == 2.2.20 == 2.4.17 == 2.4.16 == 2.2.26
CVE-2017-7668	High	June 20, 2017 6/20/17	== 2.4.25 == 2.2.32 == 2.4.24
CVE-2017-7679	High	June 20, 2017 6/20/17	>= 2.2.0 < 2.2.33 >= 2.4.0 < 2.4.26
CVE-2016-8740	Medium	December 5, 2016 12/5/16	== 2.4.20 == 2.4.23 == 2.4.18 == 2.4.22 == 2.4.19 == 2.4.17 == 2.4.21
CVE-2016-5387	High	July 19, 2016 7/19/16	>= 2.4.1 <= 2.4.23 >= 2.2.0 <= 2.2.31
CVE-2016-4979	Medium	July 6, 2016 7/6/16	== 2.4.20 == 2.4.18 == 2.4.19
CVE-2016-1546	Low	July 6, 2016 7/6/16	== 2.4.18 == 2.4.17
CVE-2015-3185	Low	July 20, 2015 7/20/15	== 2.4.1 == 2.4.6 == 2.4.0 == 2.4.12 == 2.4.3 == 2.4.8 == 2.4.4 == 2.4.10 == 2.4.7 == 2.4.13 == 2.4.2 == 2.4.9
CVE-2015-3183	Medium	July 20, 2015 7/20/15	>= 2.2.0 < 2.2.31 >= 2.4.0 < 2.4.16
CVE-2015-0253	Medium	July 20, 2015 7/20/15	== 2.4.12
CVE-2015-0228	Medium	March 8, 2015 3/8/15	<= 2.4.12
CVE-2014-8109	Low	December 29, 2014 12/29/14	== 2.4.1 == 2.4.6 == 2.4.3 == 2.4.4 == 2.4.10 == 2.4.7 == 2.4.2 == 2.4.9
CVE-2014-3583	Medium	December 15, 2014 12/15/14	== 2.4.10
CVE-2014-3581	Medium	October 10, 2014 10/10/14	== 2.4.1 == 2.4.6 == 2.4.3 == 2.4.4 == 2.4.10 == 2.4.7 == 2.4.2 == 2.4.9
CVE-2014-3523	Medium	July 20, 2014 7/20/14	== 2.4.1 == 2.4.2 == 2.4.3 == 2.4.4 == 2.4.6 == 2.4.7 == 2.4.8 == 2.4.9
CVE-2013-4352	Low	July 20, 2014 7/20/14	== 2.4.6

oracle / http_server

223 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2006-5354	High	October 18, 2006 10/18/06	== 10.1.0.5 == 9.2.0.7
CVE-2006-0435	High	January 26, 2006 1/26/06	== 9.0.3.1 == 9.0.1 == 1.0.2.2 == 9.1 == 8.1.7 == 9.2.0 == 9.0.2 == 1.0.2.1 == 1.0.2.0 == 1.0.2.1s_for_apps == 9.0.2.3 == 1.0.2.2_roll_up_2
CVE-2004-2115	Medium	December 31, 2004 12/31/04	== 9.0.1 == 8.1.7 == 9.2.0
CVE-2004-1877	Low	March 30, 2004 3/30/04	== 9.0.1 == 8.1.7 == 9.2.0
CVE-2002-0655	High	August 12, 2002 8/12/02	== 9.0.1 == 9.2.0
CVE-2002-0656	High	August 12, 2002 8/12/02	== 9.0.1 == 9.2.0
CVE-2002-0659	Medium	August 12, 2002 8/12/02	== 9.0.1 == 9.2.0
CVE-1999-1125	High	September 19, 1997 9/19/97	<= 2.1 == 1.0
CVE-1999-1068	Medium	July 23, 1997 7/23/97	== 2.1

Showing vulnerabilities for 15 products matching "http_server". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.