CVE-2024-43394 | Apache HTTP Server: SSRF on Windows due to UNC paths

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.

Published: 2025-07-10 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-43394 is rated Moderate Risk (46.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.24%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-43394

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-23 0.12% 0.24% +0.12%
2 2025-12-06 0.21% 0.12% -0.10%
3 2025-11-21 — 0.21% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-43394

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-43394

OS Trackers for CVE-2024-43394

vendor priority summary link
alpine — CVE-2024-43394: 1 source package rows (apache2); 5 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2024-43394
debian unimportant CVE-2024-43394 unimportant priority: Debian including 1 source packages (apache2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-43394
redhat medium — https://access.redhat.com/security/cve/CVE-2024-43394
suse medium CVE-2024-43394 severity moderate: SUSE including 8 source package names (apache2, apache2-2.4.64-1.1, …), 148 product×package rows across 35 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (35 product lines)): Known Not Affected 147, Fixed 1. https://www.suse.com/security/cve/CVE-2024-43394/
ubuntu medium CVE-2024-43394 medium priority: Ubuntu including 1 source packages (apache2), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, trusty, upstream, xenial): not-affected 8. https://ubuntu.com/security/CVE-2024-43394

Affected software / configurations for CVE-2024-43394

Vendor Product Version Raw CPE
apache http_server >= 2.4.0, < 2.4.64 cpe:2.3:a:apache:http_server:*:*:*:*:*:*:*:*

References for CVE-2024-43394

cvelogic Threat Intelligence