CVE-2017-15715

CRITICALNVD 8.19.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 86% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

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

A fix is available — apply it.

In Apache httpd 2.4.0 to 2.4.29, the expression specified in could match '$' to a newline character in a malicious filename, rather than matching only the end of the filename. This could be exploited in environments where uploads of some files are are externally blocked, but only by matching the trailing portion of the filename.

Live · internet exposure

458 internet-exposed hosts are running an affected version of CVE-2017-15715 right now.

across 53 countries (United States, Japan, Germany, 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
8.1
EG Score
9.0(high)
EG Risk
79(Track)
EG Risk 79/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
Severity90% × 45%
Exploitation86% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
85%
EPSS %ILE
100%
KEV
Not listed

Published

March 26, 2018

Last Modified

November 21, 2024

References (54)

Vendor Advisories for CVE-2017-15715(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.29-1ubuntu4.1) @ bionic2026-05-28ubuntu
ubuntulibapache2-mod-proxy-html (1:2.4.7-1ubuntu4.20) @ trusty2026-05-28ubuntu
redhathttpd-0:2.4.6-95.el72020-09-29redhat
redhathttpd2019-02-18redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-14.jbcs.el72019-02-18redhat
redhathttpd24-nghttp2-0:1.7.1-7.el72018-11-13redhat

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

(27 across 27 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.5(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
apache22.4.10-10 ... 2.4.10-10+deb8u9 (12 versions)2.4.10-10+deb8u12—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
apache22.4.25-3, 2.4.25-3+deb9u1, 2.4.25-3+deb9u2, 2.4.25-3+deb9u32.4.25-3+deb9u4—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

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 4× in last 7d / 15× 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-07 15:56 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:01 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-08-30 19:13 UTCEPSS rescore
  6. 2026-08-28 21:36 UTCEPSS rescore
  7. 2026-08-27 14:20 UTCEPSS rescore
  8. 2026-08-26 14:41 UTCEPSS rescore
  9. 2026-08-24 14:10 UTCEPSS rescore
  10. 2026-08-22 20:37 UTCOSV refresh
  11. 2026-08-20 22:50 UTCEPSS rescore
  12. 2026-08-19 16:59 UTCEPSS rescore
  13. 2026-08-18 13:43 UTCEPSS rescore
  14. 2026-08-16 02:10 UTCEPSS rescore
  15. 2026-08-13 21:56 UTCEPSS rescore
  16. 2026-08-08 16:32 UTCEPSS rescore
  17. 2026-08-07 16:22 UTCEPSS rescore
  18. 2026-08-07 00:04 UTCOSV refresh
  19. 2026-08-04 15:05 UTCEPSS rescore
  20. 2026-08-03 10:30 UTCEPSS rescore
  21. 2026-07-26 14:51 UTCEPSS rescore
  22. 2026-07-23 01:27 UTCEG score recompute
  23. 2026-07-22 22:06 UTCEG score recompute
  24. 2026-07-22 14:04 UTCEPSS rescore
  25. 2026-07-21 15:18 UTCOSV refresh
Show 29 more
  1. 2026-07-20 17:04 UTCEPSS rescore
  2. 2026-07-20 17:04 UTCEPSS rescore
  3. 2026-07-19 02:26 UTCEPSS rescore
  4. 2026-07-19 02:26 UTCEPSS rescore
  5. 2026-07-15 16:54 UTCEPSS rescore
  6. 2026-07-15 16:54 UTCEPSS rescore
  7. 2026-07-13 06:09 UTCEPSS rescore
  8. 2026-07-11 08:24 UTCEPSS rescore
  9. 2026-07-04 11:26 UTCOSV refresh
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-15 23:09 UTCOSV refresh
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-04 13:10 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-28 13:42 UTCEPSS rescore
  24. 2026-05-28 10:03 UTCEG score recompute
  25. 2026-05-28 10:03 UTCVendor advisory
  26. 2026-05-28 10:02 UTCGHSA enrichment
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-26 07:17 UTCEPSS rescore
  29. 2026-05-25 10:46 UTCOSV refresh

Publicly available exploits

(1 reference)

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

  • Nucleihttp/cves/2017/CVE-2017-15715.yaml
    First seen Jan 1, 2017

    Apache httpd <=2.4.29 - Arbitrary File Upload

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-15715?
CVE-2017-15715 is a critical vulnerability published on March 26, 2018. In Apache httpd 2.4.0 to 2.4.29, the expression specified in <FilesMatch> could match '$' to a newline character in a malicious filename, rather than matching only the end of the filename. This could be exploited in environments where uploads of some files are are externally blocked, but only by…
When was CVE-2017-15715 disclosed?
CVE-2017-15715 was first published in the National Vulnerability Database on March 26, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-15715 actively exploited?
CVE-2017-15715 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
What is the CVSS score of CVE-2017-15715?
CVE-2017-15715 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-15715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-15715, 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-2017-15715

Explore →

Is Your Infrastructure Affected by CVE-2017-15715?

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

Start Free Scan →Browse All CVEs