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.

346,508

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

1965 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2003-0192	Medium	August 18, 2003 8/18/03	== 2.0.42 == 2.0.35 == 2.0.37 == 2.0.44 == 2.0.39 == 2.0.41 == 2.0.32 == 2.0.38 == 2.0.45 == 2.0.36 == 2.0.43 == 2.0 == 2.0.28 == 2.0.40 == 2.0.46
CVE-2003-0253	Medium	August 18, 2003 8/18/03	== 2.0.42 == 2.0.35 == 2.0.37 == 2.0.44 == 2.0.39 == 2.0.41 == 2.0.32 == 2.0.38 == 2.0.45 == 2.0.28 == 2.0.43 == 2.0.46 == 2.0.36 == 2.0 == 2.0.40
CVE-2003-0254	Medium	August 18, 2003 8/18/03	== 2.0.42 == 2.0.35 == 2.0.37 == 2.0.44 == 2.0.39 == 2.0.41 == 2.0.32 == 2.0.38 == 2.0.45 == 2.0.43 == 2.0.36 == 2.0.46 == 2.0 == 2.0.28 == 2.0.40
CVE-2003-0189	Medium	June 9, 2003 6/9/03	== 2.0.42 == 2.0.44 == 2.0.41 == 2.0.45 == 2.0.40 == 2.0.43
CVE-2003-0245	Medium	June 9, 2003 6/9/03	== 2.0.42 == 2.0.37 == 2.0.44 == 2.0.39 == 2.0.41 == 2.0.38 == 2.0.45 == 2.0.40 == 2.0.43
CVE-2003-0132	Medium	April 11, 2003 4/11/03	>= 2.0.0 <= 2.0.44
CVE-2003-0134	Medium	April 11, 2003 4/11/03	== 2.0.42 == 2.0.35 == 2.0.37 == 2.0.44 == 2.0.39 == 2.0.41 == 2.0.9 == 2.0.32 == 2.0.38 == 2.0.36 == 2.0.43 == 2.0.45 == 2.0 == 2.0.28 == 2.0.40
CVE-2003-0083	Medium	April 2, 2003 4/2/03	>= 2.0.0 < 2.0.46 >= 1.3.0 < 1.3.26
CVE-2003-0020	Medium	March 18, 2003 3/18/03	>= 2.0.0 < 2.0.49 >= 1.3.0 < 1.3.31
CVE-2003-0016	High	February 7, 2003 2/7/03	== 2.0.42 == 2.0.37 == 2.0.39 == 2.0.41 == 2.0.38 == 2.0.40 == 2.0.36 == 2.0.43
CVE-2003-0017	Medium	February 7, 2003 2/7/03	== 2.0.42 == 2.0.37 == 2.0.39 == 2.0.41 == 2.0.38 == 2.0.40 == 2.0.36 == 2.0.43
CVE-2002-1658	Low	December 31, 2002 12/31/02	== 1.3.23 == 1.3.27 == 1.3.1 == 1.3.25 == 1.3.19 == 1.3.24 == 1.3.20 == 1.3.6 == 1.3.4 == 1.3.18 == 1.3.12 == 1.3.3 == 1.3.17 == 1.3.26 == 1.3.9 == 1.3.14 == 1.3.22 == 1.3.11
CVE-2002-1850	High	December 31, 2002 12/31/02	== 2.0.39 == 2.0.40
CVE-2002-2012	Medium	December 31, 2002 12/31/02	== 1.3.19
CVE-2002-2029	High	December 31, 2002 12/31/02	== 1.3.16 == 1.3.19 == 1.3.20 == 1.3.13 == 1.3.18 == 1.3.12 == 1.3.17 == 1.3.15 == 1.3.14 == 1.3.11
CVE-2002-2103	Medium	December 31, 2002 12/31/02	== 1.3.23 == 1.3.16 == 1.3.19 == 1.3.20 == 1.3.13 == 1.3.18 == 1.3.12 == 1.3.17 == 1.3.9 == 1.3.15 == 1.3.14 == 1.3.22 == 1.3.11
CVE-2002-2272	High	December 31, 2002 12/31/02	== 1.3.23 == 1.3.27 == 1.3.10 == 1.3.16 == 1.3.1 == 1.3.25 == 1.3.19 == 1.3.24 == 1.3.20 == 1.3.2 == 1.3.13 == 1.3.18 == 1.3.0 == 1.3 == 1.3.12 == 1.3.17 == 1.3.26 == 1.3.15 == 1.3.14 == 1.3.22 == 1.3.11
CVE-2002-1233	Low	November 4, 2002 11/4/02	== 1.3.23 == 1.3.27 == 1.3.25 == 1.3.19 == 1.3.24 == 1.3.20 == 1.3.26 == 1.3.18 == 1.3.17 == 1.3.22
CVE-2002-0839	High	October 11, 2002 10/11/02	>= 1.3.0 < 1.3.27
CVE-2002-0840	Medium	October 11, 2002 10/11/02	== 2.0.42 == 1.3.23 == 2.0.35 == 2.0.37 == 1.3.1 == 1.3.25 == 1.3.19 == 2.0.39 == 1.3.24 == 1.3.20 == 1.3.6 == 2.0.41 == 1.3.4 == 1.3.18 == 2.0.32 == 2.0.38 == 1.3 == 1.3.12 == 1.3.3 == 1.3.17 == 1.3.26 == 1.3.9 == 2.0.40 == 2.0.36 == 1.3.14 == 1.3.22 == 1.3.11 == 2.0.28 == 2.0
CVE-2002-0843	High	October 11, 2002 10/11/02	== 1.3.23 == 1.3.1 == 1.3.25 == 1.3.19 == 1.3.24 == 1.3.20 == 1.3.6 == 1.3.4 == 1.3.18 == 1.3 == 1.3.12 == 1.3.3 == 1.3.17 == 1.3.26 == 1.3.9 == 1.3.14 == 1.3.22 == 1.3.11
CVE-2002-1156	Medium	October 11, 2002 10/11/02	== 2.0.42
CVE-2002-1593	Medium	September 25, 2002 9/25/02	== 2.0.35 == 2.0.37 == 2.0.39 == 2.0.41 == 2.0.32 == 2.0.38 == 2.0.40 == 2.0.36 == 2.0.28 == 2.0
CVE-2002-0654	Medium	September 5, 2002 9/5/02	== 2.0.28-beta == 2.0.35 == 2.0.37 == 2.0.32-beta == 2.0.34-beta == 2.0.39 == 2.0.32 == 2.0.38 == 2.0.36 == 2.0.28 == 2.0
CVE-2002-0661	High	August 12, 2002 8/12/02	== 2.0.28-beta == 2.0.35 == 2.0.37 == 2.0.32-beta == 2.0.34-beta == 2.0.39 == 2.0.32 == 2.0.38 == 2.0.36 == 2.0.28 == 2.0
CVE-2002-0392	High	July 3, 2002 7/3/02	>= 2.0.0 <= 2.0.36 >= 1.2.2 <= 1.3.24
CVE-2002-0240	Medium	May 29, 2002 5/29/02	== 2.0.28-beta
CVE-2002-0249	Medium	May 29, 2002 5/29/02	== 2.0.28-beta
CVE-2002-0257	High	May 29, 2002 5/29/02	== 1.3.19 == 1.3.20 == 1.3.18 == 1.3.17 == 1.3.22
CVE-2002-1592	Medium	May 6, 2002 5/6/02	== 2.0.35 == 2.0.32 == 2.0.28 == 2.0
CVE-2002-0061	High	March 21, 2002 3/21/02	< 1.3.24 >= 2.0.0 < 2.0.34
CVE-2001-1534	Low	December 31, 2001 12/31/01	>= 1.3.11 <= 1.3.20
CVE-2001-1556	Medium	December 31, 2001 12/31/01	>= 2.0.0 < 2.0.49 >= 1.3.0 < 1.3.31
CVE-2001-1449	High	November 28, 2001 11/28/01	== 1.3.1 == 1.3.6 == 1.3.4 == 1.3.18 == 1.3 == 1.3.12 == 1.3.3 == 1.3.17 == 1.3.9 == 1.3.14 == 1.3.11
CVE-2001-0729	Medium	October 30, 2001 10/30/01	== 1.3.20
CVE-2001-0730	Medium	October 30, 2001 10/30/01	== 1.3.20
CVE-2001-0766	Critical	October 18, 2001 10/18/01	== 1.3.14
CVE-2001-0731	Medium	October 1, 2001 10/1/01	== 1.3.20
CVE-2001-1072	Medium	August 31, 2001 8/31/01	== 1.3.19 == 1.3.17 == 1.3.14
CVE-2001-1342	Medium	May 12, 2001 5/12/01	== 1.3.16 == 1.3.15 == 1.3.14 == 1.3.18 == 1.3.17 == 1.3.12 == 1.3.19
CVE-2001-0131	Low	March 12, 2001 3/12/01	== 1.3.14 == 2.0-alpha9
CVE-2001-0925	Medium	March 12, 2001 3/12/01	== 1.3.12 == 1.3.17 == 1.3.14 == 1.3.11
CVE-2001-0042	Medium	February 16, 2001 2/16/01	== 1.3
CVE-2000-0913	Medium	December 19, 2000 12/19/00	== 1.0.5 == 0.8.11 == 1.1.1 == 1.3.11 == 1.0.2 == 1.1 == 1.0 == 1.0.3 == 1.3.12 == 0.8.14
CVE-2000-0868	Medium	November 14, 2000 11/14/00	== 1.3.12
CVE-2000-0869	Medium	November 14, 2000 11/14/00	== 1.3.12
CVE-2000-1204	Medium	October 13, 2000 10/13/00	== 1.3.12 == 1.3.9 == 1.3.11
CVE-2000-0505	Medium	May 31, 2000 5/31/00	== 1.3.9 == 1.3.11 == 1.3.6 == 1.3.12
CVE-2000-1205	Low	February 1, 2000 2/1/00	== 1.3.10 == 1.3.8 == 1.3.1 == 1.3.5 == 1.3.6 == 1.3.2 == 1.3.4 == 1.3.0 == 1.3.3 == 1.3.9 == 1.3.11 == 1.3.7
CVE-1999-1293	High	December 31, 1999 12/31/99	<= 1.2.5

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.