Skip to main content
No exploitation reportedFix available

CVE-2024-43394

No exploitation reported by the sources we read.

  • Published2025-07-10
  • Fixed in2.4.64
  • WeaknessCWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Server-Side Request Forgery (SSRF) in Apache HTTP Server on Windows allows to potentially leak NTLM hashes to a malicious server via  mod_rewrite or apache expressions that pass unvalidated request input. This issue affects Apache HTTP Server: from 2.4.0 through 2.4.63. Note:  The Apache HTTP Server Project will be setting a higher bar for accepting vulnerability reports regarding SSRF via UNC paths. The server offers limited protection against administrators directing the server to open UNC paths. Windows servers should limit the hosts they will connect over via SMB based on the nature of NTLM authentication.

Timeline

dates in UTC
  1. 2025-07-1017:15CVE publishedNVD

Versions per branch

NVD · OSV
Apache HTTP Serverversion to verify
BranchAffectedFixed in
2.4≥ 2.4.0, < 2.4.642.4.64

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache HTTP Serverother versions: not affected
    Affected
    • ≥ 2.4.0, ≤ 2.4.63no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-07-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache2openSUSE:Tumbleweedall versions · fixed in 2.4.64-1.1
  • apache2MinimOSall versions · fixed in 2.4.64-r0and 5 other packages
  • apache2Debian:11all versions · fixed in 2.4.65-1~deb11u1
  • apache2Alpine:v3.24all versions · fixed in 2.4.64-r0
  • apache2Alpine:v3.23all versions · fixed in 2.4.64-r0
  • apache2Alpine:v3.22all versions · fixed in 2.4.64-r0
  • apache2Alpine:v3.21all versions · fixed in 2.4.64-r0
  • apache2Alpine:v3.20all versions · fixed in 2.4.64-r0

6 more package ranges on OSV.dev

Vendor advisories

  • CVE-2024-43394 Red Hat Product Security

    httpd: Apache HTTP Server: SSRF on Windows due to UNC paths

Full record on NVD

Fix

  1. Update Apache HTTP Server to 2.4.64

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2025-07-10
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-gxxm-rhpx-j39m

Frequently asked questions

What is CVE-2024-43394?

Server-Side Request Forgery (SSRF) in Apache HTTP Server on Windows allows to potentially leak NTLM hashes to a malicious server via  mod_rewrite or apache expressions that pass unvalidated request input. This issue affects Apache HTTP Server: from 2.4.0 through 2.4.63. Note:  The Apache HTTP Server Project will be setting a higher bar for accepting vulnerability reports regarding SSRF via UNC paths. The server offers limited protection against administrators directing the server to open UNC paths. Windows servers should limit the hosts they will connect over via SMB based on the nature of NTLM authentication.

Is CVE-2024-43394 actively exploited?

Active exploitation of CVE-2024-43394 has not been confirmed. Its EPSS score was 1.3% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-43394?

CVE-2024-43394 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running Apache HTTP Server? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record