Strix
26.1K

CVE-2017-5664

UnknownEPSS 16.57%

Last modified

CVE-2017-5664 is a vulnerability of currently unknown severity. 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. EPSS estimates a 16.57% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
16.57%

96.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
ApacheTomcat7.0.0—
ApacheTomcat7.0.1—
ApacheTomcat7.0.2—
ApacheTomcat7.0.3—
ApacheTomcat7.0.4—
ApacheTomcat7.0.5—
ApacheTomcat7.0.6—
ApacheTomcat7.0.7—
ApacheTomcat7.0.8—
ApacheTomcat7.0.9—
ApacheTomcat7.0.10—
ApacheTomcat7.0.11—
ApacheTomcat7.0.12—
ApacheTomcat7.0.13—
ApacheTomcat7.0.14—
ApacheTomcat7.0.15—
ApacheTomcat7.0.16—
ApacheTomcat7.0.17—
ApacheTomcat7.0.18—
ApacheTomcat7.0.19—
ApacheTomcat7.0.20—
ApacheTomcat7.0.21—
ApacheTomcat7.0.22—
ApacheTomcat7.0.23—
ApacheTomcat7.0.24—
ApacheTomcat7.0.25—
ApacheTomcat7.0.26—
ApacheTomcat7.0.27—
ApacheTomcat7.0.28—
ApacheTomcat7.0.29—
ApacheTomcat7.0.30—
ApacheTomcat7.0.31—
ApacheTomcat7.0.32—
ApacheTomcat7.0.33—
ApacheTomcat7.0.34—
ApacheTomcat7.0.35—
ApacheTomcat7.0.36—
ApacheTomcat7.0.37—
ApacheTomcat7.0.38—
ApacheTomcat7.0.39—
ApacheTomcat7.0.40—
ApacheTomcat7.0.41—
ApacheTomcat7.0.42—
ApacheTomcat7.0.43—
ApacheTomcat7.0.44—
ApacheTomcat7.0.45—
ApacheTomcat7.0.46—
ApacheTomcat7.0.47—
ApacheTomcat7.0.48—
ApacheTomcat7.0.49—

Showing 50 of 135 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2017-5664?
Severity scoring for CVE-2017-5664 is pending analysis. The EPSS model estimates a 16.57% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5664?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-5664?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST