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

CVE-2017-5664 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.0.0.M21, 8.5.15, 8.0.44, 7.0.78); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2017-5664? CVE-2017-5664 is a high-severity security vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 9.0.0.M1, <= 9.0.0.M20. It is fixed in 9.0.0.M21, 8.5.15, 8.0.44, 7.0.78.
2. How severe is CVE-2017-5664? CVE-2017-5664 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.tomcat:tomcat are affected by CVE-2017-5664? org.apache.tomcat:tomcat (maven) versions >= 9.0.0.M1, <= 9.0.0.M20 is affected.
4. Is there a fix for CVE-2017-5664? Yes. CVE-2017-5664 is fixed in 9.0.0.M21, 8.5.15, 8.0.44, 7.0.78. Upgrade to this version or later.
5. Is CVE-2017-5664 exploitable, and should I be worried? Whether CVE-2017-5664 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2017-5664 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2017-5664?
   • Upgrade org.apache.tomcat:tomcat to 9.0.0.M21 or later
   • Upgrade org.apache.tomcat:tomcat to 8.5.15 or later
   • Upgrade org.apache.tomcat:tomcat to 8.0.44 or later
   • Upgrade org.apache.tomcat:tomcat to 7.0.78 or later