Critical SSRF Vulnerability in Apache HTTP Server (apache2) - CVE-2024-43204
Summary
CVE-2024-43204: 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 C... Affects apache2 across 2 version ranges.
< 2.4.64-r0
>= da5873e80d6eee7a0838793bf68f1d0254745fbb, < 7e926454793abd7d71b6afc8bd1ec1648752c6ad
Fixed in 2.4.64-r0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache HTTP Server, commonly referred to as Apache, is one of the most widely used web server software applications. It provides a robust and flexible platform for serving web content and is known for its modular architecture, allowing users to extend its functionality through various modules. However, certain configurations can expose Apache to vulnerabilities, such as the SSRF (Server-Side Request Forgery) issue identified in CVE-2024-43204, which can lead to unauthorized outbound requests.
Vulnerability Detail
The vulnerability arises from a flaw in the mod_proxy module of Apache HTTP Server, which allows an attacker to send outbound proxy requests to a URL they control. This requires a specific and unlikely configuration where the mod_headers module is set to modify the Content-Type header based on user input. If exploited, this could lead to data leakage or further attacks on internal services, making it a significant security concern.
How To Fix
Minimum fixed version
2.4.64-r0
This is the first release that contains the fix.
sudo apk add --upgrade apache2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If an immediate upgrade is not feasible, consider disabling the mod_proxy module or ensuring that mod_headers is not configured to modify the Content-Type header based on user input. This can help mitigate the risk until a proper update can be applied.
Conclusion
The SSRF vulnerability in Apache HTTP Server (CVE-2024-43204) poses a significant risk to users who have specific configurations enabled. It is crucial to upgrade to the patched version to ensure the security of your web applications. Additionally, utilizing tools like Vulert can help maintain awareness of potential vulnerabilities in your software.
See every vulnerability recorded for apache2 →
FAQ
CVE-2024-43204 is a critical SSRF vulnerability in the Apache HTTP Server that allows attackers to send unauthorized outbound requests.
If you are using Apache HTTP Server versions prior to 2.4.64, especially with mod_proxy and mod_headers configured, your server may be vulnerable.
Exploitation of this vulnerability can lead to data leakage, unauthorized access to internal services, and potential further attacks on your network.
Yes, upgrading to Apache HTTP Server version 2.4.64 or later will patch this vulnerability.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using a manifest file. You can check your application for vulnerabilities without signup using the Vulert playground.
References
Related vulnerabilities
Recent vulnerabilities recorded for apache2.
