HTTP ServerWeb server / proxy · Apache
CVE-2024-38475
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper escaping of output in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to map URLs to filesystem locations that are permitted to be served by the server but are not intentionally/directly reachable by any URL, resulting in code execution or source code disclosure. Substitutions in server context that use a backreferences or variables as the first segment of the substitution are affected. Some unsafe RewiteRules will be broken by this change and the rewrite flag "UnsafePrefixStat" can be used to opt back in once ensuring the substitution is appropriately constrained.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper escaping in mod_rewrite allows attackers to map URLs to filesystem locations beyond intended boundaries using backreferences or variables as the first substitution segment, enabling code execution or source code disclosure of files the server can serve but shouldn't expose.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
HTTP ServerWeb server / proxy
>= 2.4.0, < 2.4.60all versions< 10.2.1.14-75sv< 10.2.1.14-75sv< 10.2.1.14-75sv< 10.2.1.14-75sv< 10.2.1.14-75svCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache HTTP Server versionRun 'httpd -v' or 'apache2 -v' to get the server version numberAffected if Version is 2.4.0 through 2.4.59 (inclusive)
-
Confirm mod_rewrite module is loadedCheck for 'mod_rewrite.c' in the output of 'httpd -M' or 'apache2ctl -M', or look for 'LoadModule rewrite_module' in the httpd.conf configuration fileAffected if mod_rewrite is loaded and available
-
Inspect RewriteRule configurations for backreference or variable usageSearch all configuration files (httpd.conf, included conf files, vhost configs) for RewriteRule directives. Examine the substitution string (the second argument) for use of $N backreferences (like $1, $2) or %{VARIABLE} in the first path segment before any literal directory prefixAffected if Any RewriteRule uses a backreference or variable as the first segment of the substitution URL (e.g., 'RewriteRule ^(.*)$ $1/path' or 'RewriteRule ^(.*) %{REQUEST_URI}/extra') in server context configuration
-
Determine if rules are in server context vs .htaccessCheck whether the RewriteRule appears in the main server configuration file, virtual host configuration, or within a <Directory> block (server context) rather than only in .htaccess filesAffected if The vulnerable RewriteRule pattern is defined in httpd.conf, vhost config, or <Directory> blocks rather than exclusively in .htaccess files
A user is affected if they run Apache 2.4.0-2.4.59 with mod_rewrite enabled and have RewriteRules using backreferences or variables as the first segment of substitution in server configuration context.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.6010.2.1.14-75sv
Upgrade to Apache HTTP Server 2.4.60 or later, audit all RewriteRules using backreferences or variables in substitutions, constrain substitutions to prevent path traversal, and test thoroughly after applying the fix.
Apache HTTP Server 2.4.60
- Identify all Apache HTTP Server instances running version 2.4.0 through 2.4.59
- For NetApp Ontap 9: Contact NetApp support for the specific patch per security.netapp.com advisories
- For SMA firmware devices: Contact Dell EMC (or the respective vendor) for firmware updates beyond 10.2.1.14-75sv
- Stop the Apache HTTP Server service before upgrading
- Download Apache HTTP Server 2.4.60 or later from httpd.apache.org
- Extract and install the new version, preserving custom configurations
- Restart the Apache HTTP Server service
- Verify mod_rewrite rules function correctly - note that some unsafe RewriteRules may break and require the 'UnsafePrefixStat' flag
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in HTTP Server
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-38475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data