Unauthenticated server crash via hostname-less proxy URI
Published Jul 1, 2024 · Updated Nov 3, 2025
NULL pointer dereference in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows remote attackers to crash the server. ap_proxy_determine_connection and ap_proxy_create_hdrbrgd accepted a parsed proxy URI without a hostname, then used the null hostname. The request must reach a mod_proxy configuration that processes the crafted hostname-less URI; the consequence is a server-process crash.
Summary
What happened
NULL pointer dereference in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows remote attackers to crash the server. ap_proxy_determine_connection and ap_proxy_create_hdrbrgd accepted a parsed proxy URI without a hostname, then used the null hostname. The request must reach a mod_proxy configuration that processes the crafted hostname-less URI; the consequence is a server-process crash.
The record
- CVE
- CVE-2024-38477
- Published
- Jul 1, 2024
- Updated
- Nov 3, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.4.0 <=2.4.59
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo