CVE-2024-43204: Apache HTTP Server · Server-Side Request Forgery (SSRF)
Affects Apache HTTP ServerSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.4.64 soon.
Data as of 26 Oct 2026, 06:15 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.64
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade redhat/httpd to 2.4.64.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Red Hatredhat/httpdpkg:rpm/redhat/httpdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade of all Apache HTTP Server instances to version 2.4.64 or later, which contains the official fix for CVE-2024-43204. 2. Review and audit server configurations to identify and disable any unnecessary use of mod_proxy and mod_headers modules, particularly configurations that modify the Content-Type header based on client input. 3. Implement strict input validation and sanitization on HTTP headers to prevent injection of malicious values that could be used to trigger SSRF. 4. Employ network segmentation and firewall rules to restrict outbound HTTP requests from web servers to only trusted destinations, limiting the potential impact of SSRF exploitation. 5. Monitor server logs and network traffic for unusual outbound requests or patterns indicative of SSRF attempts. 6. Conduct penetration testing and vulnerability scanning focused on SSRF vectors to identify and remediate similar weaknesses proactively. 7. Educate system administrators and developers about the risks of SSRF and secure configuration practices for Apache modules.
Description
SSRF in Apache HTTP Server with mod_proxy loaded allows an attacker to send outbound proxy requests to a URL controlled by the attacker. Requires an unlikely configuration where mod_headers is configured to modify the Content-Type request or response header with a value provided in the HTTP request. Users are recommended to upgrade to version 2.4.64 which fixes this issue.