Threats / Apache / CVE-2024-38475
CVE-2024-38475
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Apache HTTP Server vulnerability
Apache HTTP Server mod_rewrite contains improper output escaping allowing attackers to access restricted filesystem locations, potentially enabling code execution or source disclosure.
Verdict
Today item — known-exploited.
An attacker exploits mod_rewrite escaping flaws to bypass URL access controls and reach unintended server files. This can lead to arbitrary code execution or exposure of sensitive source code, with active exploitation confirmed in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
224 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-01).
Probability (EPSS)
EPSS 0.99957 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apache, HTTP Server. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-116 CWE-116.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-116 · CWE-116
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious URL that exploits improper escaping in mod_rewrite rules to map to filesystem paths normally inaccessible through standard routing.
Business
Attackers gain unauthorized access to restricted application files and backend resources.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I retrieve executable files or scripts stored outside the web root by leveraging the rewrite bypass to serve them directly.
Business
Source code, configuration files, and credentials become exposed to unauthorized parties.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code by accessing and invoking scripts or binaries that the web server process can reach but should not serve.
Business
Complete server compromise occurs, enabling data theft, malware deployment, and lateral movement within infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by apacheCNA
Credited with finding itOrange Tsai (@orange_8361) from DEVCOREfinder