dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-38472

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
High EPSS 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 on Windows allows to potentially leak NTLM hashes to a malicious server via SSRF and malicious requests or content Users are recommended to upgrade to version 2.4.60 which fixes this issue.  Note: Existing configurations that access UNC paths will have to configure new directive "UNCList" to allow access during request processing.

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 when running on Windows systems. The flaw allows attackers to potentially leak NTLM hashes to a malicious server through specially crafted SSRF requests or content, likely exploiting how Apache handles UNC path resolution on Windows.

MitigationUpgrade Apache HTTP Server to version 2.4.60 or later. If the configuration accesses UNC paths, implement the new UNCList directive to control and restrict UNC access during request processing.

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. Identify the operating system
    Run 'systeminfo | findstr /B /C:"OS Name"' or check system properties to confirm Windows is in use
    Affected if The server is not running Windows (this vulnerability only affects Windows systems)
  2. Determine installed Apache HTTP Server version
    Run 'httpd -v' (Windows) or 'apache2 -v' to get the server version, or check the Apache error log startup banner
    Affected if The installed version is 2.4.0 through 2.4.59 inclusive (versions below 2.4.60 are affected)
  3. Verify if the server processes requests involving UNC paths
    Examine Apache configuration files (httpd.conf, included .conf files) for references to UNC paths in the format \\servername\sharename or the UNCList directive, and check if any VirtualHost or location blocks handle URLs that could resolve to UNC paths
    Affected if UNC path handling is configured or possible (the vulnerability exploits UNC path resolution on Windows to leak NTLM hashes)
  4. Check for NTLM authentication configuration
    Review Apache configuration for 'NTLMAuthoritative off' or related NTLM/Windows authentication modules (mod_auth_ntlm, mod_auth_sspi) that enable Windows authentication
    Affected if NTLM or Windows-integrated authentication is enabled (this is what gets leaked to the attacker's server)
  5. Review external content or proxy configurations
    Check if the server is configured as a proxy (mod_proxy) or uses 'ProxyPass' directives that could be triggered with attacker-controlled URLs, or if mod_rewrite with [P] flag is used
    Affected if The server can be induced to make outbound requests to attacker-specified URLs (the SSRF vector that triggers UNC resolution)

The server is affected if it runs on Windows with Apache HTTP Server versions 2.4.0-2.4.59, has UNC path handling enabled or accessible, and uses NTLM authentication or processes requests that could trigger outbound connections to attacker-controlled locations.

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. If the configuration accesses UNC paths, implement the new UNCList directive to control and restrict UNC access during request processing.

Recommended fix High confidence

Apache HTTP Server 2.4.60

  1. 1. Identify all Apache HTTP Server instances running on Windows that are version 2.4.0 through 2.4.59
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Download Apache HTTP Server version 2.4.60 from the official Apache distribution site (httpd.apache.org)
  4. 4. Backup the current Apache configuration files (httpd.conf and included configuration files)
  5. 5. Stop the Apache HTTP Server service
  6. 6. Install Apache HTTP Server 2.4.60
  7. 7. Restore the backed-up configuration files
  8. 8. If using UNC paths in your configuration, add the new 'UNCList' directive to allow access during request processing
Caveat Configurations using UNC paths will require the new 'UNCList' directive to be configured to maintain functionality 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
  • 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-38472 — 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-38472 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