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
Critical September 16, 2021 9/16/21
< 2.4.49
Critical September 16, 2021 9/16/21
<= 2.4.48
High August 16, 2021 8/16/21
>= 2.4.17, < 2.4.49
High June 15, 2021 6/15/21
= 1.15.17
= 2.4.47
Medium June 10, 2021 6/10/21
>= 2.4.6, <= 2.4.46
Medium June 10, 2021 6/10/21
>= 2.4.0, <= 2.4.46
High June 10, 2021 6/10/21
>= 2.4.41, <= 2.4.46
High June 10, 2021 6/10/21
>= 2.4.0, <= 2.4.46
High June 10, 2021 6/10/21
>= 2.4.0, <= 2.4.46
Critical June 10, 2021 6/10/21
>= 2.4.0, <= 2.4.46
Medium June 10, 2021 6/10/21
>= 2.4.39, <= 2.4.46
High August 7, 2020 8/7/20
>= 2.4.20, < 2.4.46
Critical August 7, 2020 8/7/20
>= 2.4.32, <= 2.4.43
Medium August 7, 2020 8/7/20
>= 2.4.1, <= 2.4.23
High August 7, 2020 8/7/20
>= 2.4.20, < 2.4.44
Medium April 2, 2020 4/2/20
>= 2.4.0, <= 2.4.41
Medium April 1, 2020 4/1/20
>= 2.4.0, <= 2.4.41
Critical September 26, 2019 9/26/19
>= 2.4.18, <= 2.4.39
Medium September 26, 2019 9/26/19
>= 2.4.0, <= 2.4.39
High September 26, 2019 9/26/19
= 2.4.33
= 2.4.34
= 2.4.35
= 2.4.37
= 2.4.38
Medium September 25, 2019 9/25/19
>= 2.4.0, <= 2.4.39
Medium August 15, 2019 8/15/19
>= 2.4.20, <= 2.4.39
High August 13, 2019 8/13/19
>= 2.4.20, < 2.4.40
Medium June 11, 2019 6/11/19
>= 2.4.34, <= 2.4.38
Medium June 11, 2019 6/11/19
>= 2.4.17, <= 2.4.38
Medium June 11, 2019 6/11/19
>= 2.4.0, <= 2.4.38
High April 8, 2019 4/8/19
>= 2.4.17, <= 2.4.38
High April 8, 2019 4/8/19
>= 2.4.0, <= 2.4.38
Medium April 8, 2019 4/8/19
= 2.4.37
= 2.4.38
Medium January 30, 2019 1/30/19
= 2.4.17
= 2.4.18
= 2.4.20
= 2.4.23
= 2.4.25
= 2.4.26
= 2.4.27
= 2.4.28
= 2.4.29
= 2.4.30
= 2.4.33
= 2.4.34
= 2.4.35
= 2.4.37
Medium January 30, 2019 1/30/19
>= 2.4.0, <= 2.4.37
High January 30, 2019 1/30/19
= 2.4.37
Medium September 25, 2018 9/25/18
>= 2.4.17, <= 2.4.34
Medium August 14, 2018 8/14/18
= 2.2.0
= 2.2.2
= 2.2.3
= 2.2.4
= 2.2.6
= 2.2.8
= 2.2.9
= 2.2.10
= 2.2.11
= 2.2.12
= 2.2.13
= 2.2.14
= 2.2.15
= 2.2.16
= 2.2.17
= 2.2.18
= 2.2.19
= 2.2.20
= 2.2.21
= 2.2.22
= 2.2.23
= 2.2.24
= 2.2.25
= 2.2.26
= 2.2.27
= 2.2.29
= 2.2.31
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.4
= 2.4.6
= 2.4.7
= 2.4.9
= 2.4.10
= 2.4.12
= 2.4.16
= 2.4.17
= 2.4.18
= 2.4.20
= 2.4.23
Medium July 26, 2018 7/26/18
= 2.2.15-60
Medium July 18, 2018 7/18/18
= 2.4.33
Medium June 18, 2018 6/18/18
>= 2.4.18, <= 2.4.30
= 2.4.33
Medium March 26, 2018 3/26/18
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.4
= 2.4.6
= 2.4.7
= 2.4.9
= 2.4.10
= 2.4.12
= 2.4.16
= 2.4.17
= 2.4.18
= 2.4.20
= 2.4.23
= 2.4.25
= 2.4.26
= 2.4.27
= 2.4.28
= 2.4.29
Medium March 26, 2018 3/26/18
>= 2.4.0, <= 2.4.29
Low March 26, 2018 3/26/18
>= 2.4.0, <= 2.4.29
Medium March 26, 2018 3/26/18
<= 2.4.29
Medium March 26, 2018 3/26/18
<= 2.4.29
Medium March 26, 2018 3/26/18
<= 2.4.29
Critical March 26, 2018 3/26/18
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.4
= 2.4.6
= 2.4.7
= 2.4.9
= 2.4.10
= 2.4.12
= 2.4.16
= 2.4.17
= 2.4.18
= 2.4.20
= 2.4.23
= 2.4.25
= 2.4.26
= 2.4.27
= 2.4.28
= 2.4.29
Low March 9, 2018 3/9/18
< 2.4.23
High September 18, 2017 9/18/17
<= 2.2.34
= 2.4.0
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.4
= 2.4.6
= 2.4.7
= 2.4.9
= 2.4.10
= 2.4.12
= 2.4.16
= 2.4.17
= 2.4.18
= 2.4.20
= 2.4.23
= 2.4.25
= 2.4.26
= 2.4.27
Medium July 27, 2017 7/27/17
= 2.4.0
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.6
= 2.4.7
= 2.4.8
= 2.4.9
= 2.4.10
= 2.4.12
= 2.4.14
= 2.4.16
= 2.4.19
= 2.4.20
= 2.4.21
= 2.4.22
= 2.4.23
Medium July 27, 2017 7/27/17
= 2.4.0
= 2.4.1
= 2.4.2
= 2.4.3
= 2.4.6
= 2.4.7
= 2.4.8
= 2.4.9
= 2.4.10
= 2.4.12
= 2.4.14
= 2.4.16
= 2.4.19
= 2.4.20
= 2.4.21
= 2.4.22
= 2.4.23
High July 27, 2017 7/27/17
>= 2.2.0, <= 2.2.31
>= 2.4.1, <= 2.4.23
Medium July 26, 2017 7/26/17
= 2.4.24
= 2.4.25

oracle / http_server

115 vulnerabilities found
Title Severity Exploit Date Affected versions
Low January 17, 2007 1/17/07
= 9.0.1.5
High October 18, 2006 10/18/06
= 9.2.0.7
High October 18, 2006 10/18/06
= 9.2.0.7
High October 18, 2006 10/18/06
= 9.2.0.7
High October 18, 2006 10/18/06
= 9.2.0.7
High October 18, 2006 10/18/06
= 9.2.0.7
High October 18, 2006 10/18/06
= 9.2.0.7
= 10.1.0.5
High January 26, 2006 1/26/06
= 1.0.2.0
= 1.0.2.1
= 1.0.2.1s_for_apps
= 1.0.2.2
= 1.0.2.2_roll_up_2
= 8.1.7
= 9.0.1
= 9.0.2
= 9.0.2.3
= 9.0.3.1
= 9.1
= 9.2.0
Medium December 31, 2004 12/31/04
= 8.1.7
= 9.0.1
= 9.2.0
Low March 30, 2004 3/30/04
= 8.1.7
= 9.0.1
= 9.2.0
High August 12, 2002 8/12/02
= 9.0.1
= 9.2.0
High August 12, 2002 8/12/02
= 9.0.1
= 9.2.0
Medium August 12, 2002 8/12/02
= 9.0.1
= 9.2.0
High September 19, 1997 9/19/97
<= 2.1
= 1.0
Medium July 23, 1997 7/23/97
= 2.1

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.