CVE-2024-38472

HIGHNVD 7.58.5▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.5 because EPSS predicts 68% probability of exploitation within the next 30 days (top 0.7% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 1,524 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS PROB: 69%CVSS: 7.5Exploit: Elevated riskExposed: 1,524

A fix is available — apply it.

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.

Live · internet exposure

1,524 internet-exposed hosts are running an affected version of CVE-2024-38472 right now.

across 81 countries (United States, Germany, Japan, France, United Kingdom)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
8.5(high)
EG Risk
80(Track)
EG Risk 80/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation68% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
69%
EPSS %ILE
99%
KEV
Not listed

Published

July 1, 2024

Last Modified

July 1, 2025

References (4)

Vendor Advisories for CVE-2024-38472(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2024-09-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.60-r0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-15 03:08 UTCEPSS rescore
  4. 2026-09-15 03:08 UTCEPSS rescore
  5. 2026-09-12 14:59 UTCEPSS rescore
  6. 2026-09-11 09:35 UTCEPSS rescore
  7. 2026-09-08 21:58 UTCEPSS rescore
  8. 2026-09-06 13:46 UTCEPSS rescore
  9. 2026-09-05 15:26 UTCEPSS rescore
  10. 2026-09-04 13:59 UTCEPSS rescore
  11. 2026-09-04 05:05 UTCEPSS rescore
  12. 2026-09-02 14:10 UTCEPSS rescore
  13. 2026-09-02 00:12 UTCOSV refresh
  14. 2026-09-01 13:52 UTCEPSS rescore
  15. 2026-08-30 19:15 UTCEPSS rescore
  16. 2026-08-28 21:39 UTCEPSS rescore
  17. 2026-08-26 14:44 UTCEPSS rescore
  18. 2026-08-24 14:15 UTCEPSS rescore
  19. 2026-08-23 00:18 UTCEPSS rescore
  20. 2026-08-21 23:47 UTCEPSS rescore
  21. 2026-08-20 22:53 UTCEPSS rescore
  22. 2026-08-19 17:02 UTCEPSS rescore
  23. 2026-08-16 02:35 UTCOSV refresh
  24. 2026-08-16 02:13 UTCEPSS rescore
  25. 2026-08-15 01:28 UTCEPSS rescore
Show 70 more
  1. 2026-08-13 21:59 UTCEPSS rescore
  2. 2026-08-12 13:49 UTCEPSS rescore
  3. 2026-08-11 13:40 UTCEPSS rescore
  4. 2026-08-07 16:25 UTCEPSS rescore
  5. 2026-08-05 19:16 UTCEPSS rescore
  6. 2026-08-03 10:34 UTCEPSS rescore
  7. 2026-08-03 10:34 UTCEPSS rescore
  8. 2026-08-01 04:14 UTCEPSS rescore
  9. 2026-08-01 04:14 UTCEPSS rescore
  10. 2026-07-31 20:12 UTCOSV refresh
  11. 2026-07-30 16:26 UTCEPSS rescore
  12. 2026-07-30 16:26 UTCEPSS rescore
  13. 2026-07-30 01:29 UTCEPSS rescore
  14. 2026-07-28 15:34 UTCEPSS rescore
  15. 2026-07-26 14:53 UTCEPSS rescore
  16. 2026-07-24 14:16 UTCEPSS rescore
  17. 2026-07-23 02:38 UTCEG score recompute▼ 0.50
  18. 2026-07-22 14:07 UTCEPSS rescore
  19. 2026-07-22 14:07 UTCEPSS rescore
  20. 2026-07-21 15:23 UTCEPSS rescore
  21. 2026-07-21 15:23 UTCEPSS rescore
  22. 2026-07-20 17:06 UTCEPSS rescore
  23. 2026-07-19 14:30 UTCEPSS rescore
  24. 2026-07-19 14:30 UTCEPSS rescore
  25. 2026-07-19 02:28 UTCEPSS rescore
  26. 2026-07-19 02:28 UTCEPSS rescore
  27. 2026-07-16 17:02 UTCEPSS rescore
  28. 2026-07-15 16:56 UTCEPSS rescore
  29. 2026-07-15 16:56 UTCEPSS rescore
  30. 2026-07-14 03:25 UTCOSV refresh
  31. 2026-07-13 22:29 UTCEPSS rescore
  32. 2026-07-13 06:11 UTCEPSS rescore
  33. 2026-07-11 08:26 UTCEPSS rescore
  34. 2026-07-11 08:26 UTCEPSS rescore
  35. 2026-07-09 19:09 UTCEPSS rescore
  36. 2026-07-06 16:26 UTCEPSS rescore
  37. 2026-07-01 15:05 UTCEPSS rescore
  38. 2026-06-28 04:55 UTCEPSS rescore
  39. 2026-06-28 04:55 UTCEPSS rescore
  40. 2026-06-26 00:46 UTCOSV refresh
  41. 2026-06-25 13:49 UTCEPSS rescore
  42. 2026-06-24 14:04 UTCEPSS rescore
  43. 2026-06-24 14:04 UTCEPSS rescore
  44. 2026-06-23 21:32 UTCEPSS rescore
  45. 2026-06-23 21:32 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-18 17:51 UTCEPSS rescore
  48. 2026-06-17 17:52 UTCEPSS rescore
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-16 17:52 UTCEPSS rescore
  51. 2026-06-15 17:47 UTCEPSS rescore
  52. 2026-06-13 22:59 UTCEPSS rescore
  53. 2026-06-13 22:59 UTCEPSS rescore
  54. 2026-06-12 23:11 UTCEPSS rescore
  55. 2026-06-10 22:17 UTCEPSS rescore
  56. 2026-06-08 14:16 UTCEPSS rescore
  57. 2026-06-08 14:11 UTCOSV refresh
  58. 2026-06-05 22:46 UTCEPSS rescore
  59. 2026-06-05 22:46 UTCEPSS rescore
  60. 2026-05-31 00:15 UTCEPSS rescore
  61. 2026-05-31 00:15 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-27 13:40 UTCEPSS rescore
  65. 2026-05-26 07:18 UTCEPSS rescore
  66. 2026-05-26 07:18 UTCEPSS rescore
  67. 2026-05-26 07:18 UTCEPSS rescore
  68. 2026-05-23 23:05 UTCEG score recompute
  69. 2026-05-23 23:05 UTCVendor advisory
  70. 2026-05-23 23:05 UTCGHSA enrichment

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmrmtwoj/apache-vulnerability-testing
    First seen Oct 5, 2024

    Apache HTTP Server Vulnerability Testing Tool | PoC for CVE-2024-38472 , CVE-2024-39573 , CVE-2024-38477 , CVE-2024-38476 , CVE-2024-38475 , CVE-2024-38474 , CVE-2024-38473 , CVE-2023-38709

    Open source ↗
  • GitHub PoCAbdurahmon3236/CVE-2024-38472
    First seen Aug 3, 2024
    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-38472.yaml
    First seen Jan 1, 2024

    Apache HTTPd Windows UNC - Server-Side Request Forgery

    Open source ↗

Frequently asked(5)

What is CVE-2024-38472?
CVE-2024-38472 is a high vulnerability published on July 1, 2024. 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…
When was CVE-2024-38472 disclosed?
CVE-2024-38472 was first published in the National Vulnerability Database on July 1, 2024, with the most recent update on July 1, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-38472 actively exploited?
CVE-2024-38472 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 69% probability of exploitation in the next 30 days, which ranks it in the top 0.7% of all scored CVEs.
What is the CVSS score of CVE-2024-38472?
CVE-2024-38472 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2024-38472?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-38472, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-38472

Explore →

Is Your Infrastructure Affected by CVE-2024-38472?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs