Vulnerability Database

417,459

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

344 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium July 28, 2010 7/28/10
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.16
Medium June 18, 2010 6/18/10
= 2.2.9
= 2.2.10
= 2.2.11
= 2.2.12
= 2.2.13
= 2.2.14
= 2.2.15
= 2.3.4-alpha
= 2.3.5-alpha
High March 5, 2010 3/5/10
>= 2.0.37, < 2.0.64
>= 2.2.0, < 2.2.15
>= 2.3.0, < 2.3.7
Medium March 5, 2010 3/5/10
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.15
Medium March 5, 2010 3/5/10
= 2.2
= 2.2.0
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.6
= 2.2.8
= 2.2.9
= 2.2.11
= 2.2.12
= 2.2.13
= 2.2.14
Medium February 5, 2010 2/5/10
= 2.0.44
Low February 5, 2010 2/5/10
= 2.0.44
Medium February 2, 2010 2/2/10
<= 1.3.41
= 0.8.11
= 0.8.14
= 1.0
= 1.0.3
= 1.0.5
= 1.1
= 1.2
= 1.2.4
= 1.2.5
= 1.2.6
= 1.3
= 1.3.0
= 1.3.1
= 1.3.2
= 1.3.3
= 1.3.4
= 1.3.10
= 1.3.11
= 1.3.12
= 1.3.13
= 1.3.14
= 1.3.15
= 1.3.17
= 1.3.18
= 1.3.19
= 1.3.20
= 1.3.22
= 1.3.23
= 1.3.24
= 1.3.25
= 1.3.26
= 1.3.27
= 1.3.28
= 1.3.29
= 1.3.30
= 1.3.31
= 1.3.32
= 1.3.33
= 1.3.34
= 1.3.35
= 1.3.36
= 1.3.37
= 1.3.38
= 1.3.39
= 1.3.40
Medium December 4, 2009 12/4/09
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.17
Critical November 9, 2009 11/9/09
<= 2.2.14
Medium November 3, 2009 11/3/09
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.17
High October 13, 2009 10/13/09
>= 2.2.0, < 2.2.14
Low September 8, 2009 9/8/09
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.14
Medium September 8, 2009 9/8/09
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.14
High July 10, 2009 7/10/09
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.12
High July 5, 2009 7/5/09
>= 2.2.0, < 2.2.12
Medium June 8, 2009 6/8/09
>= 2.2.0, < 2.2.12
High June 8, 2009 6/8/09
>= 2.2.0, < 2.2.12
Medium June 8, 2009 6/8/09
>= 2.2.0, < 2.2.12
Medium May 28, 2009 5/28/09
= 2.2.0
= 2.2.1
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.7
= 2.2.8
= 2.2.9
= 2.2.10
Medium April 23, 2009 4/23/09
= 2.2.11
Medium August 6, 2008 8/6/08
<= 2.0.63
>= 2.2.0, <= 2.2.9
Medium June 13, 2008 6/13/08
>= 2.0.35, < 2.0.64
>= 2.2.0, < 2.2.9
Medium May 13, 2008 5/13/08
= 2.0
= 2.0.9
= 2.0.28
= 2.0.28-beta
= 2.0.32
= 2.0.32-beta
= 2.0.34-beta
= 2.0.35
= 2.0.36
= 2.0.37
= 2.0.38
= 2.0.39
= 2.0.40
= 2.0.41
= 2.0.42
= 2.0.43
= 2.0.44
= 2.0.45
= 2.0.46
= 2.0.47
= 2.0.48
= 2.0.49
= 2.0.50
= 2.0.51
= 2.0.52
= 2.0.53
= 2.0.54
= 2.0.55
= 2.0.56
= 2.0.57
= 2.0.58
= 2.0.59
= 2.0.60
= 2.0.61
= 2.1
= 2.1.1
= 2.1.2
= 2.1.3
= 2.1.4
= 2.1.5
= 2.1.6
= 2.1.7
= 2.1.8
= 2.2
= 2.2.1
= 2.2.2
= 2.2.3
= 2.2.4
Medium January 25, 2008 1/25/08
>= 2.2.0, < 2.2.23
>= 2.4.1, < 2.4.3
Low January 25, 2008 1/25/08
>= 2.2.0, < 2.2.12
Medium January 12, 2008 1/12/08
= 2.2.0
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.5
= 2.2.6
= 2.2.8
High January 12, 2008 1/12/08
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.6
Medium January 12, 2008 1/12/08
>= 2.2.0, < 2.2.8
>= 2.0.35, < 2.0.63
Low January 8, 2008 1/8/08
= 2.2
= 2.2.1
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.6
Medium January 8, 2008 1/8/08
>= 1.3.2, <= 1.3.39
>= 2.0.35, <= 2.0.61
>= 2.2.0, <= 2.2.6
Medium January 8, 2008 1/8/08
= 2.2
= 2.2.1
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.6
Medium December 21, 2007 12/21/07
= 2.2.6
Medium December 13, 2007 12/13/07
>= 1.3.0, <= 1.3.39
>= 2.0.35, <= 2.0.61
>= 2.2.0, <= 2.2.6
Medium December 3, 2007 12/3/07
= 2.0.46
= 2.0.47
= 2.0.48
= 2.0.49
= 2.0.50
= 2.0.51
= 2.0.52
= 2.0.53
= 2.0.54
= 2.0.55
= 2.0.57
= 2.0.58
= 2.0.59
= 2.1.1
= 2.1.2
= 2.1.3
= 2.1.4
= 2.1.5
= 2.1.6
= 2.1.7
= 2.1.8
= 2.2.0
= 2.2.2
= 2.2.3
= 2.2.4
Medium September 14, 2007 9/14/07
>= 2.2.0, < 2.2.6
>= 2.0.0, < 2.0.61
Medium August 23, 2007 8/23/07
>= 2.2.0, < 2.2.6
>= 2.0.35, < 2.0.61
Medium June 27, 2007 6/27/07
>= 2.2.0, < 2.2.6
>= 2.0.0, < 2.0.61
>= 1.3.2, < 1.3.39
Medium June 27, 2007 6/27/07
>= 2.2.0, < 2.2.6
>= 2.0.37, < 2.0.61
Medium June 20, 2007 6/20/07
= 2.0.59
= 2.2.4
Medium June 20, 2007 6/20/07
>= 2.2.0, < 2.2.6
>= 2.0.0, < 2.0.61
>= 1.3.0, < 1.3.39
Medium June 4, 2007 6/4/07
= 2.2.4
Low April 13, 2007 4/13/07
= 2.2.3
Medium April 13, 2007 4/13/07
= 2.2.3
Medium April 13, 2007 4/13/07
= 2.2.3
High October 16, 2006 10/16/06
= 2.0
= 2.0.9
= 2.0.28
= 2.0.28-beta
= 2.0.32
= 2.0.32-beta
= 2.0.34-beta
= 2.0.35
= 2.0.36
= 2.0.37
= 2.0.38
= 2.0.39
= 2.0.40
= 2.0.41
= 2.0.42
= 2.0.43
= 2.0.44
= 2.0.45
= 2.0.46
= 2.0.47
= 2.0.48
= 2.0.49
= 2.0.50
= 2.0.51
= 2.0.52
= 2.0.53
= 2.0.54
= 2.0.55
= 2.0.56
= 2.0.57
= 2.0.58
= 2.1
= 2.1.1
= 2.1.2
= 2.1.3
= 2.1.4
= 2.1.5
= 2.1.6
= 2.2
= 2.2.1
= 2.2.2
= 2.2.3
Medium August 14, 2006 8/14/06
= 2.0.58
= 2.2.2
= 2.2.3
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
Medium July 28, 2006 7/28/06
>= 1.3.3, < 1.3.35
Medium December 31, 2005 12/31/05
= 2.0
= 2.0.9
= 2.0.28
= 2.0.28-beta
= 2.0.32
= 2.0.35
= 2.0.36
= 2.0.37
= 2.0.38
= 2.0.39
= 2.0.40
= 2.0.41
= 2.0.42
= 2.0.43
= 2.0.44
= 2.0.45
= 2.0.46
= 2.0.47
= 2.0.48
= 2.0.49
= 2.0.50
= 2.0.51
= 2.0.52
= 2.0.53
= 2.0.54
= 2.0.55

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

Running Http Server on internet-facing hosts?

Knowing a product's CVEs is half the job; the other half is knowing every place it is exposed. Attack surface management continuously maps your external assets and the software they run.

What is attack surface management? →

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.