Apache HTTP Server
9 published vulnerabilities name this product.
As the CNAs write it in their CVE records (vendor and product); the versions are theirs.
| CVE | Vulnerable versions | Title | Severity | Published | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2020-11985 | 2.4.1 to 2.4.23 | IP address spoofing when proxying using mod_remoteip and mod_rewrite For configurations using proxying with mod_remoteip and certain mod_rew | MEDIUM 5.3 | 7.0 % | ||
| CVE-2020-11993 | 2.4.20 to 2.4.43 | Apache HTTP Server versions 2.4.20 to 2.4.43 When trace/debug was enabled for the HTTP/2 module and on certain traffic edge patterns, loggin | HIGH 7.5 | 56 % | ||
| CVE-2020-11984 | 2.4.32 to 2.4.44 | Apache HTTP server 2.4.32 to 2.4.44 mod_proxy_uwsgi info disclosure and possible RCE | CRITICAL 9.8 | 90 % | ||
| CVE-2020-9490 | 2.4.20 to 2.4.43 | Apache HTTP Server versions 2.4.20 to 2.4.43. A specially crafted value for the 'Cache-Digest' header in a HTTP/2 request would result in a | HIGH 7.5 | 89 % | ||
| CVE-2019-10082 | 2.4.18 to 2.4.39 | In Apache HTTP Server 2.4.18-2.4.39, using fuzzed network input, the http/2 session handling could be made to read memory after being freed, | CRITICAL 9.1 | 17 % | ||
| CVE-2019-10097 | 2.4.32 to 2.4.39 | In Apache HTTP Server 2.4.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using the "PROXY" protocol, | HIGH 7.2 | 53 % | ||
| CVE-2019-10092 | 2.4.0 to 2.4.39 | In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page. An attacker could | MEDIUM 6.1 | 81 % | ||
| CVE-2019-10098 | 2.4.0 to 2.4.39 | In Apache HTTP server 2.4.0 to 2.4.39, Redirects configured with mod_rewrite that were intended to be self-referential might be fooled by en | MEDIUM 6.1 | 74 % | ||
| CVE-2019-10081 | 2.4.20 to 2.4.39 | HTTP/2 (2.4.20 through 2.4.39) very early pushes, for example configured with "H2PushResource", could lead to an overwrite of memory in the | HIGH 7.5 | 15 % |