dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-43204

HIGH · 7.5 CVSS v3.1 Published 2025-07-10
Fix available
A fix is available. Upgrade to 2.4.64 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
SSRF in Apache HTTP Server with mod_proxy loaded allows an attacker to send outbound proxy requests to a URL controlled by the attacker.  Requires an unlikely configuration where mod_headers is configured to modify the Content-Type request or response header with a value provided in the HTTP request. Users are recommended to upgrade to version 2.4.64 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

This is a Server-Side Request Forgery (SSRF) vulnerability in Apache HTTP Server where mod_proxy is loaded and mod_headers is configured in an unlikely manner to modify the Content-Type request or response header using a value taken directly from the HTTP request. This allows an attacker to cause the server to send outbound proxy requests to arbitrary URLs they control.

MitigationUpgrade Apache HTTP Server to version 2.4.64 and audit the mod_headers configuration to ensure it is not using user-supplied input to modify Content-Type headers, which is an unusual and dangerous configuration.

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.64

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 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 get the installed version number
    Affected if Version is 2.4.0 or higher but lower than 2.4.64
  2. Verify mod_proxy is loaded
    Run 'httpd -M' or 'apache2ctl -M' and look for 'proxy_module' in the output, or check for 'LoadModule proxy_module' in the httpd.conf configuration files
    Affected if mod_proxy is loaded and enabled
  3. Verify mod_headers is loaded
    Run 'httpd -M' or 'apache2ctl -M' and look for 'headers_module' in the output, or check for 'LoadModule headers_module' in the httpd.conf configuration files
    Affected if mod_headers is loaded and enabled
  4. Inspect mod_headers configuration for Content-Type manipulation
    Search all configuration files (httpd.conf, include files, .conf files in conf.d or conf.modules.d) for any 'Header set Content-Type' or 'Header always set Content-Type' directives
    Affected if A directive modifies the Content-Type header
  5. Check if Content-Type uses request-supplied input
    Examine any Content-Type header directive found and determine if it uses variables that pull from the incoming HTTP request, such as %{HTTP_Content-Type}, %{CONTENT_TYPE}, or similar expressions that directly echo back user input
    Affected if The Content-Type header modification uses a value taken directly from the HTTP request (e.g., %{HTTP_Content-Type})

You are affected if you are running Apache 2.4.0 to 2.4.63 with mod_proxy and mod_headers loaded, and you have a mod_headers configuration that echoes back the request's Content-Type header value to modify outbound requests.

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.64 or later
Fixed in 2.4.64
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.64 and audit the mod_headers configuration to ensure it is not using user-supplied input to modify Content-Type headers, which is an unusual and dangerous configuration.

Recommended fix High confidence

2.4.64

  1. Check current Apache HTTP Server version (e.g., httpd -v or apache2 -v)
  2. Download Apache HTTP Server version 2.4.64 from the official Apache distribution site (httpd.apache.org) or use your system's package manager
  3. Install the new version following standard upgrade procedures for your operating system
  4. Restart the Apache HTTP Server service (e.g., systemctl restart httpd or systemctl restart apache2)
  5. Verify the installed version is 2.4.64 (httpd -v)
  6. Ensure mod_headers and mod_proxy configurations are still functioning correctly
Caveat Standard Apache upgrade; review module configurations and test applications after upgrading

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43204 — 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-43204 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