CVE-2024-38473·Apache vulnerability
Encoding problem in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows request URLs with incorrect encoding to be sent to backend services, potentially bypassing authentication via crafted requests. Users are recommended to upgrade to version 2.4.60, which fixes this issue.
- Severity
- high
- Software
- Apache
- Fixed in
- 2.4.60
- Published
- 2024-07-01
Affected versions
From: 2.4.0
Until: 2.4.60
Fixed in: 2.4.60
How to fix this CVE
Upgrade Apache HTTP Server to version 2.4.60 or later to resolve an encoding bypass vulnerability in mod_proxy that could allow authenticated attackers to circumvent backend authentication mechanisms. Prioritize this update for any deployment where mod_proxy forwards requests to backend services, as the vulnerability requires valid credentials but can lead to authentication bypass on downstream systems.
sudo dnf update httpd && sudo systemctl restart httpdDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST|GET /[a-zA-Z0-9/_-]*%(?:2e|2f|5c|3a)[a-zA-Z0-9/_-]* HTTP/1\.[01].*X-Forwarded-For|Proxy-AuthorizationWAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Implement a WAF rule to block HTTP requests to proxy endpoints (e.g., paths handled by mod_proxy) that contain URL-encoded special characters (%, hex-encoded octets) in the path segment, particularly %2e, %2f, %5c, and %3a, while allowing legitimate encoded parameters in query strings only.How to check if you are affected
- Run 'apache2ctl -v' or 'httpd -v' to check your current Apache version; if it reports 2.4.0 through 2.4.59, your installation is vulnerable
- Execute 'apache2ctl -M | grep proxy' (or 'httpd -M | grep proxy' on RHEL/CentOS) to confirm mod_proxy is loaded; if it appears, the vulnerable component is active
- Search your Apache access logs for requests containing URL-encoded characters followed by backend authentication failures: grep -i 'proxy.*%' /var/log/apache2/access.log | grep -i '401\|403'
- After applying the patch, re-run 'apache2ctl -v' to confirm version 2.4.60 or later is installed, then verify mod_proxy still loads and test a backend proxy request completes without encoding anomalies
FAQ
What is CVE-2024-38473?
CVE-2024-38473 is an encoding flaw in Apache mod_proxy that allows malformed or specially-crafted request URLs to bypass authentication validation rules on backend services, even when the frontend Apache server enforces authentication.
Is CVE-2024-38473 being actively exploited?
No, CVE-2024-38473 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available; however, the high CVSS score (8.1) warrants prompt patching.
What versions of Apache are affected by CVE-2024-38473?
Apache HTTP Server versions 2.4.0 through 2.4.59 are vulnerable; version 2.4.60 and later contain the fix.
How do I check if my server is vulnerable to CVE-2024-38473?
Run 'apache2ctl -v' (or 'httpd -v' on Red Hat-based systems) and check if the version is between 2.4.0 and 2.4.59; if mod_proxy is also enabled (check with 'apache2ctl -M | grep proxy'), your setup is vulnerable.
Does Defensia detect CVE-2024-38473?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Apache is installed on a monitored server, CVE-2024-38473 will appear in your dashboard with remediation steps.
Related Apache CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-38473. Free for 1 server.
Get started free