CVE-2017-5664

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 16.6%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 17%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are forwarded to the error page. This means that the request is presented to the error page with the original HTTP method. If the error page is a static file, expected behaviour is to serve content of the file as if processing a GET request, regardless of the actual HTTP method. The Default Servlet in Apache Tomcat 9.0.0.M1 to 9.0.0.M20, 8.5.0 to 8.5.14, 8.0.0.RC1 to 8.0.43 and 7.0.0 to 7.0.77 did not do this. Depending on the original request this could lead to unexpected and undesirable results for static error pages including, if the DefaultServlet is configured to permit writes, the replacement or removal of the custom error page. Notes for other user provided error pages: (1) Unless explicitly coded otherwise, JSPs ignore the HTTP method. JSPs used as error pages must must ensure that they handle any error dispatch as a GET request, regardless of the actual method. (2) By default, the response generated by a Servlet does depend on the HTTP method. Custom Servlets used as error pages must ensure that they handle any error dispatch as a GET request, regardless of the actual method.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
54(Track)
EG Risk 54/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
Severity75% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
17%
EPSS %ILE
97%
KEV
Not listed

Published

June 6, 2017

Last Modified

June 17, 2026

References (76)

Vendor Advisories for CVE-2017-5664(4)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat8 (8.0.38-2ubuntu2.2) @ zesty2026-05-22ubuntu
redhattomcat6-0:6.0.24-111.el6_92017-10-30redhat
redhatpicketlink-federation-0:2.5.4-17.SP15_redhat_1.1.ep6.el62017-09-05redhat
redhatpicketlink-federation-0:2.5.4-17.SP15_redhat_1.1.ep6.el52017-09-05redhat
redhatjboss-ec2-eap-0:7.5.17-1.Final_redhat_4.ep6.el62017-09-05redhat
redhatpicketlink-federation-0:2.5.4-17.SP15_redhat_1.1.ep6.el72017-09-05redhat
redhatpatch2017-09-05redhat
redhattomcat72017-08-21redhat
redhattomcat7-0:7.0.54-25_patch_05.ep6.el72017-08-21redhat
redhattomcat-0:7.0.69-12.el7_32017-07-27redhat
redhatpatch2017-07-25redhat
redhattomcat-native-0:1.2.8-10.redhat_10.ep7.el72017-07-25redhat

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

(5 across 4 ecosystems)
Debian:8(2)
PackageVulnerable rangeFixed inDependents
tomcat77.0.56-3 ... 7.0.56-3+deb8u9 (11 versions)7.0.56-3+deb8u11—
tomcat88.0.14-1 ... 8.0.14-1+deb8u9 (10 versions)8.0.14-1+deb8u10—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
tomcat77.0.28-4 ... 7.0.28-4+deb7u9 (14 versions)7.0.28-4+deb7u14—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
tomcat88.5.14-18.5.14-1+deb9u1—
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat:tomcat7.0.35 ... 7.0.77 (29 versions)7.0.78—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

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 6× in last 7d / 20× 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.

Showing the most recent 100 of 138 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-5664?
CVE-2017-5664 is a high vulnerability published on June 6, 2017. The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are forwarded to the error page. This means that the request is presented to the error page with the original…
When was CVE-2017-5664 disclosed?
CVE-2017-5664 was first published in the National Vulnerability Database on June 6, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5664 actively exploited?
CVE-2017-5664 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17% probability of exploitation in the next 30 days, which ranks it in the top 3.1% of all scored CVEs.
What is the CVSS score of CVE-2017-5664?
CVE-2017-5664 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-5664?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5664, 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-5664

Explore →

Is Your Infrastructure Affected by CVE-2017-5664?

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

Start Free Scan →Browse All CVEs