dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-39573

HIGH · 7.5 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2.4.60 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Potential SSRF in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to cause unsafe RewriteRules to unexpectedly setup URL's to be handled by mod_proxy. Users are recommended to upgrade to version 2.4.60, which fixes this issue.

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 confidence

SSRF vulnerability in Apache HTTP Server's mod_rewrite module where unsafe RewriteRules can unexpectedly cause URLs to be handled by mod_proxy, potentially allowing attackers to make the server request arbitrary URLs.

MitigationUpgrade to Apache HTTP Server 2.4.60 or later. Review existing RewriteRule configurations to ensure they do not allow untrusted user input to influence proxy destinations.

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
Affected:>= 2.4.0, < 2.4.60
OntapApplication
Affected:= 9

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to display server version information
    Affected if Version is 2.4.x where x is less than 60 (e.g., 2.4.59 or lower)
  2. Verify mod_rewrite module is loaded
    Check for 'LoadModule rewrite_module' in httpd.conf or run 'httpd -M' / 'apache2ctl -M' to list loaded modules
    Affected if mod_rewrite is present and loaded by the server
  3. Verify mod_proxy module is loaded
    Check for 'LoadModule proxy_module' in httpd.conf or run 'httpd -M' / 'apache2ctl -M' to list loaded modules
    Affected if mod_proxy is present and loaded by the server
  4. Inspect RewriteRule configurations
    Search all configuration files (httpd.conf, included conf files, .htaccess) for RewriteRule directives, particularly those using the [P] flag or passing variables to proxy destinations
    Affected if RewriteRules exist that forward requests to dynamic URLs (e.g., using query strings, path parameters, or environment variables) without strict validation

Server is affected if it runs Apache 2.4.0 to 2.4.59 with both mod_rewrite and mod_proxy enabled, and has RewriteRule configurations that could allow untrusted input to influence proxy destinations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4.60 or later
Fixed in 2.4.60
Interim mitigation

Upgrade to Apache HTTP Server 2.4.60 or later. Review existing RewriteRule configurations to ensure they do not allow untrusted user input to influence proxy destinations.

Recommended fix High confidence

Apache HTTP Server 2.4.60

  1. Check current Apache HTTP Server version using 'httpd -v' or 'apache2 -v'
  2. Stop the Apache HTTP Server service using 'systemctl stop httpd' (or 'apache2ctl stop')
  3. Download Apache HTTP Server 2.4.60 from the official Apache website (httpd.apache.org) or your distribution's package repository
  4. Install the new version using your package manager (e.g., 'yum update httpd', 'apt-get install apache2', or compile from source)
  5. Verify the installation was successful by checking 'httpd -v' shows version 2.4.60
  6. Start the Apache HTTP Server service using 'systemctl start httpd' (or 'apache2ctl start')
  7. Test that the server is running properly and review RewriteRule configurations to ensure they do not allow unexpected proxy behavior
Caveat Review mod_rewrite and mod_proxy configurations; test thoroughly before deploying to production as behavioral changes in rewrite handling may affect existing applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39573 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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