dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-38476

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2.4.60 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Vulnerability in core of Apache HTTP Server 2.4.59 and earlier are vulnerably to information disclosure, SSRF or local script execution via backend applications whose response headers are malicious or exploitable. 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

Apache HTTP Server 2.4.59 and earlier contains a vulnerability in its core component that allows information disclosure, SSRF, or local script execution when processing malicious or exploitable response headers from backend applications. The vulnerability stems from insufficient validation of backend response headers before processing.

MitigationUpgrade Apache HTTP Server to version 2.4.60 or later to remediate this vulnerability.

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
Clustered Data OntapOperating system
Affected:= 9.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to retrieve the server version. On Windows, check the executable properties. On Linux, also check package manager output like 'rpm -q httpd' or 'dpkg -l apache2'
    Affected if Version is 2.4.59 or earlier, or any version from 2.4.0 through 2.4.59 (less than 2.4.60)
  2. Verify if mod_proxy is loaded
    Run 'httpd -M' or 'apache2ctl -M' to list loaded modules. Look for mod_proxy, mod_proxy_http, mod_proxy_connect, or mod_proxy_balancer in the output
    Affected if One or more proxy modules are loaded and the server acts as a reverse proxy to backend applications
  3. Check for reverse proxy configuration
    Examine httpd.conf or included configuration files for 'ProxyPass', 'ProxyPassReverse', or 'ProxyRequests' directives. Also check for 'SSLProxyEngine On' indicating backend SSL connections
    Affected if The server is configured to forward requests to backend applications via ProxyPass or similar directives
  4. Inspect backend response header handling
    Review configuration for 'ProxyPassReverse' directives and any custom header manipulation rules using 'RequestHeader' or 'ResponseHeader' directives
    Affected if Backend response headers are being processed or manipulated without additional validation rules

You are affected if your Apache HTTP Server version is 2.4.0 through 2.4.59 and the server is configured as a reverse proxy forwarding requests to backend applications.

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 Apache HTTP Server to version 2.4.60 or later to remediate this vulnerability.

Recommended fix High confidence

Apache HTTP Server 2.4.60

  1. Upgrade Apache HTTP Server from any version < 2.4.60 to version 2.4.60 or later
  2. For NetApp Clustered Data Ontap 9.0, consult vendor security advisory for patch availability
Caveat Minor version within 2.4.x series typically backward compatible; review Apache 2.4.60 release notes for any behavioral changes

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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