ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2017-5664

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 origina…

Published Jun 6, 2017 · catalog updated Oct 15, 2026 · the affected product

Check this week

CVE-2017-5664 is not in CISA KEV. FIRST estimates a 16.57% chance of exploitation in the next 30 days. Check whether you run the affected product.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
16.57%
Remediation
Advisory link
Affected products
cpe apache/tomcat

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/tomcat7.0.0
  • cpe apache/tomcat7.0.1
  • cpe apache/tomcat7.0.2
  • cpe apache/tomcat7.0.3
  • cpe apache/tomcat7.0.4
  • cpe apache/tomcat8.0.0
  • cpe apache/tomcat8.5.0
  • cpe apache/tomcat9.0.0

How to fix CVE-2017-5664

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2017-5664 is not in CISA KEV. FIRST estimates a 16.57% chance of exploitation in the next 30 days. Check whether you run the affected product.

Which versions are affected?

Compare what you have installed with 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 8.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-755: Improper Handling of Exceptional Conditions. EPSS 16.57%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 6, 2017 · NIST NVD

    Detected

    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

  2. Oct 15, 2026 · NIST NVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2017-5664

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2017-5664

    30-day exploitation probability 16.6%

    first.org
  • NIST NVDVulnerability recordCVE-2017-5664

    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 pag

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.