Vulnerability Database

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 Exploit Date Affected Version
CVE-2007-6203
Low December 3, 2007 12/3/07
== 2.0.58
== 2.2.0
== 2.0.47
== 2.0.50
== 2.2.2
== 2.1.3
== 2.2.4
== 2.0.55
== 2.1.2
== 2.1.1
== 2.0.52
== 2.1.7
== 2.0.53
== 2.0.57
== 2.0.51
== 2.0.49
== 2.1.6
== 2.1.4
== 2.0.48
== 2.1.5
== 2.2.3
== 2.0.46
== 2.0.54
== 2.0.59
== 2.1.8
CVE-2007-4465
Medium September 14, 2007 9/14/07
>= 2.2.0 < 2.2.6
>= 2.0.0 < 2.0.61
CVE-2007-3847
Medium August 23, 2007 8/23/07
>= 2.2.0 < 2.2.6
>= 2.0.35 < 2.0.61
CVE-2006-5752
Low June 27, 2007 6/27/07
>= 2.2.0 < 2.2.6
>= 2.0.0 < 2.0.61
>= 1.3.2 < 1.3.39
CVE-2007-1863
Medium June 27, 2007 6/27/07
>= 2.2.0 < 2.2.6
>= 2.0.37 < 2.0.61
CVE-2007-3303
Low June 20, 2007 6/20/07
== 2.2.4
== 2.0.59
CVE-2007-3304
Low June 20, 2007 6/20/07
>= 2.2.0 < 2.2.6
>= 2.0.0 < 2.0.61
>= 1.3.0 < 1.3.39
CVE-2007-1862
Medium June 4, 2007 6/4/07
== 2.2.4
CVE-2007-1742
Low April 13, 2007 4/13/07
== 2.2.3
CVE-2007-1743
Low April 13, 2007 4/13/07
== 2.2.3
CVE-2007-1741
Medium April 13, 2007 4/13/07
== 2.2.3
CVE-2006-4154
Medium October 16, 2006 10/16/06
== 2.0.42
== 2.2
== 2.0.58
== 2.0.47
== 2.1
== 2.0.28-beta
== 2.0.56
== 2.0.50
== 2.1.3
== 2.0.35
== 2.0.37
== 2.0.55
== 2.1.2
== 2.2.2
== 2.1.1
== 2.0.32-beta
== 2.0.44
== 2.0.34-beta
== 2.0.39
== 2.0.52
== 2.0.53
== 2.0.57
== 2.0.51
== 2.0.41
== 2.0.49
== 2.1.6
== 2.0.9
== 2.0.32
== 2.0.38
== 2.1.4
== 2.0.48
== 2.0.45
== 2.0.40
== 2.1.5
== 2.0.36
== 2.0.46
== 2.0.54
== 2.0.43
== 2.2.3
== 2.0.28
== 2.0
== 2.2.1
CVE-2006-4110
Low August 14, 2006 8/14/06
== 2.0.58
== 2.2.2
== 2.2.3
CVE-2006-3747
High July 28, 2006 7/28/06
>= 2.2.0 < 2.2.3
>= 1.3.28 < 1.3.37
>= 2.0.46 < 2.0.59
CVE-2006-3918
Low July 28, 2006 7/28/06
>= 1.3.3 < 1.3.35
CVE-2005-3357
Medium December 31, 2005 12/31/05
== 2.0.42
== 2.0.47
== 2.0.50
== 2.0.35
== 2.0.37
== 2.0.55
== 2.0.44
== 2.0.39
== 2.0.52
== 2.0.53
== 2.0.51
== 2.0.28-beta
== 2.0.41
== 2.0.49
== 2.0.9
== 2.0.32
== 2.0.38
== 2.0.48
== 2.0.45
== 2.0.40
== 2.0.36
== 2.0.46
== 2.0.54
== 2.0.43
== 2.0.28
== 2.0
CVE-2005-3352
Low December 13, 2005 12/13/05
== 2.2
< 1.3.35
>= 2.0 < 2.0.56
CVE-2005-2970
Medium October 25, 2005 10/25/05
>= 2.0.36 < 2.0.55
CVE-2005-2700
High September 6, 2005 9/6/05
>= 2.0.35 < 2.0.55
CVE-2005-2728
Medium August 30, 2005 8/30/05
== 2.0.42
== 2.0.47
== 2.0.50
== 2.0.35
== 2.0.37
== 2.0.44
== 2.0.39
== 2.0.52
== 2.0.53
== 2.0.51
== 2.0.28-beta
== 2.0.41
== 2.0.49
== 2.0.9
== 2.0.32
== 2.0.38
== 2.0.48
== 2.0.45
== 2.0.40
== 2.0.36
== 2.0.46
== 2.0.43
== 2.0.28
== 2.0
CVE-2005-1268
Medium August 5, 2005 8/5/05
>= 2.0.35 <= 2.0.54
CVE-2005-2088
Low July 5, 2005 7/5/05
>= 2.0.35 < 2.0.55
CVE-2005-1344
High May 2, 2005 5/2/05
== 2.0.52
CVE-2004-0940
High February 9, 2005 2/9/05
>= 1.3 <= 1.3.32
CVE-2004-0942
Medium February 9, 2005 2/9/05
<= 2.0.52
CVE-2004-0811
High December 31, 2004 12/31/04
== 2.0.51
CVE-2004-1387
Low December 31, 2004 12/31/04
== 1.3.31
CVE-2004-2343
High December 31, 2004 12/31/04
<= 2.0.47
CVE-2004-0263
Medium November 23, 2004 11/23/04
== 2.0.42
== 1.3.23
== 2.0.47
== 1.3.27
== 1.0.5
== 1.1.1
== 2.0.35
== 2.0.37
== 2.0.44
== 1.3.1
== 1.3.25
== 1.3.28
== 1.3.19
== 2.0.39
== 1.3.24
== 1.3.20
== 1.0.2
== 1.3.7
== 1.1
== 1.3.6
== 2.0.28-beta
== 2.0.41
== 1.3.4
== 1.2.5
== 2.0.9
== 1.0
== 1.3.18
== 2.0.32
== 1.0.3
== 2.0.38
== 1.3
== 1.3.12
== 2.0.48
== 1.3.3
== 1.3.17
== 2.0.45
== 1.3.26
== 1.3.9
== 2.0.40
== 2.0.36
== 1.3.14
== 1.3.29
== 2.0.46
== 1.3.22
== 1.3.11
== 2.0.43
== 1.2
== 2.0.28
== 2.0
CVE-2004-0885
High November 3, 2004 11/3/04
== 2.0.42
== 2.0.47
== 2.0.50
== 2.0.35
== 2.0.37
== 2.0.44
== 2.0.39
== 2.0.52
== 2.0.51
== 2.0.41
== 2.0.49
== 2.0.38
== 2.0.48
== 2.0.45
== 2.0.40
== 2.0.36
== 2.0.46
== 2.0.43
CVE-2004-0747
High October 20, 2004 10/20/04
>= 2.0.35 < 2.0.51
CVE-2004-0748
Medium October 20, 2004 10/20/04
>= 2.0.35 < 2.0.51
CVE-2004-0751
Medium October 20, 2004 10/20/04
>= 2.0.44 < 2.0.51
CVE-2004-0786
Medium October 20, 2004 10/20/04
>= 2.0.35 < 2.0.51
CVE-2004-0809
Medium September 16, 2004 9/16/04
>= 2.0.35 < 2.0.51
CVE-2004-0492
High August 6, 2004 8/6/04
== 1.3.27
== 1.3.28
== 1.3.31
== 1.3.26
== 1.3.29
CVE-2004-0493
Medium August 6, 2004 8/6/04
== 2.0.47
== 2.0.49
== 2.0.48
CVE-2004-0488
High July 7, 2004 7/7/04
>= 2.0.35 < 2.0.50
CVE-2004-0174
High May 4, 2004 5/4/04
<= 2.0.49
CVE-2004-0173
Medium April 15, 2004 4/15/04
== 1.0.5
== 0.8.11
== 1.1.1
== 1.0.2
== 1.1
== 1.2.5
== 1.0
== 1.0.3
== 1.3
== 0.8.14
== 1.2
CVE-2003-0993
High March 29, 2004 3/29/04
== 1.3.23
== 1.3.27
== 1.3.1
== 1.3.25
== 1.3.28
== 1.3.19
== 1.3.24
== 1.3.20
== 1.3.7
== 1.3
== 1.3.22
== 1.3.3
== 1.3.4
== 1.3.18
== 1.3.11
== 1.3.12
== 1.3.6
== 1.3.29
== 1.3.14
== 1.3.17
== 1.3.26
== 1.3.9
CVE-2004-0113
Medium March 29, 2004 3/29/04
== 2.0.42
== 2.0.47
== 2.0.35
== 2.0.37
== 2.0.44
== 2.0.39
== 2.0.41
== 2.0.38
== 2.0.48
== 2.0.45
== 2.0.40
== 2.0.36
== 2.0.46
== 2.0.43
CVE-2004-1834
Low March 20, 2004 3/20/04
== 2.0.42
== 2.0.47
== 2.0.35
== 2.0.37
== 2.0.44
== 2.0.39
== 2.0.28-beta
== 2.0.41
== 2.0.49
== 2.0.9
== 2.0.32
== 2.0.38
== 2.0.48
== 2.0.45
== 2.0.40
== 2.0.36
== 2.0.46
== 2.0.43
== 2.0.28
== 2.0
CVE-2003-0987
High March 3, 2004 3/3/04
<= 1.3.30
CVE-2004-1082
High February 3, 2004 2/3/04
== 1.3.23
== 1.3.27
== 1.3.1
== 1.3.25
== 1.3.28
== 1.3.19
== 1.3.24
== 1.3.20
== 1.3.7
== 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.29
== 1.3.22
== 1.3.11
CVE-2003-1307
Low December 31, 2003 12/31/03
== 2.0.42
== 2.0.47
== 2.0.28-beta
== 2.0.35
== 2.0.37
== 2.0.32-beta
== 2.0.44
== 2.0.34-beta
== 2.0.39
== 2.0.28
== 2.0.38
== 2.0.43
== 2.0.9
== 2.0
== 2.0.36
== 2.0.45
== 2.0.46
== 2.0.32
== 2.0.40
== 2.0.41
== 2.0.48
CVE-2003-1418
Low December 31, 2003 12/31/03
== 1.3.23
== 1.3.27
== 1.3.25
== 1.3.24
== 1.3.26
== 1.3.22
CVE-2003-0542
High November 3, 2003 11/3/03
== 2.0.42
== 1.3.23
== 2.0.47
== 1.3.27
== 2.0.35
== 2.0.37
== 2.0.44
== 1.3.1
== 1.3.25
== 1.3.12
== 1.3.24
== 1.3.26
== 1.3.17
== 1.3.18
== 1.3.28
== 2.0.32
== 1.3.6
== 1.3.9
== 2.0.38
== 2.0.39
== 2.0.41
== 1.3
== 1.3.19
== 1.3.20
== 1.3.3
== 1.3.4
== 2.0.45
== 1.3.14
== 2.0
== 2.0.43
== 1.3.11
== 1.3.22
== 2.0.46
== 2.0.28
== 2.0.40
== 2.0.36
CVE-2003-0789
High November 3, 2003 11/3/03
>= 2.0.35 < 2.0.48
CVE-2003-0460
Medium August 27, 2003 8/27/03
<= 1.3.27

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

Frequently Asked Questions

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.