CVE-2024-39573 | Apache HTTP Server: mod_rewrite proxy handler substitution

Potential SSRF in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to cause unsafe RewriteRules to unexpectedly setup URL's to be handled by mod_proxy. Users are recommended to upgrade to version 2.4.60, which fixes this issue.

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

CVE-2024-39573 is rated Moderate Risk (59.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.58%). 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-39573

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 3.12% 2.58% -0.53%
2 2026-04-14 3.16% 3.12% -0.04%
3 2026-03-04 — 3.16% —

Full EPSS history (59 records total)

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

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-39573

OS Trackers for CVE-2024-39573

vendor priority summary link
alpine — CVE-2024-39573: 1 source package rows (apache2); 7 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 0. https://security.alpinelinux.org/vuln/CVE-2024-39573
debian not yet assigned CVE-2024-39573 not yet assigned 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-39573
gentoo low CVE-2024-39573: 1 GLSA(s) (202409-31), 1 atom(s) (www-servers/apache); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-39573
redhat medium — https://access.redhat.com/security/cve/CVE-2024-39573
suse medium CVE-2024-39573 severity moderate: SUSE including 315 source package names (2.8:apache2-utils-2.4.58-150600.5.11.1, 4.3.13.9.57.7:apache2-2.4.51-150400.6.29.1, …), 511 product×package rows across 71 product lines (Container bci/php-apache, Container suse/manager/4.3/proxy-httpd, … (71 product lines)): Fixed 280, Known Affected 231. https://www.suse.com/security/cve/CVE-2024-39573/
ubuntu medium CVE-2024-39573 medium priority: Ubuntu including 1 source packages (apache2), 11 status rows across 11 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): released 8, needs-triage 3. https://ubuntu.com/security/CVE-2024-39573

Affected software / configurations for CVE-2024-39573

Vendor Product Version Raw CPE
apache http_server >= 2.4.0, < 2.4.60 cpe:2.3:a:apache:http_server:*:*:*:*:*:*:*:*
netapp ontap 9 cpe:2.3:a:netapp:ontap:9:*:*:*:*:*:*:*

References for CVE-2024-39573

cvelogic Threat Intelligence