CVE-2017-5664: 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 Apache advisory covers CVE-2017-5664 in Apache Tomcat.
- CVE-2017-5664
Key facts
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Apache Tomcat 9.0.0.M1 to 9.0.0.M20; Apache Tomcat 8.5.0 to 8.5.14; Apache Tomcat 8.0.0.RC1 to 8.0.43 and 1 more below
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
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.
Text from the source record.
- Apache Tomcat 9.0.0.M1 to 9.0.0.M20
- Apache Tomcat 8.5.0 to 8.5.14
- Apache Tomcat 8.0.0.RC1 to 8.0.43
- Apache Tomcat 7.0.0 to 7.0.77
Official advisory · medium-confidence parse· fetched ·verify at source
End-of-life dates for Apache Tomcat
More Apache Software Foundation advisories
CVE-2026-103119Oct 20, 2026Buffer under-read vulnerability in Apache Tomcat meantCVE-2026-101356Oct 20, 2026Incorrect object recycling and re-use vulnerability in Apache TomcatCVE-2026-101296Oct 20, 2026Apache Tomcat: JNDIRealm bind credential validation fails open for non-GSSAPI SASLCVE-2026-93446Oct 20, 2026Apache Tomcat: Possible TLS 1.3 connection failuresCVE-2026-88041Oct 20, 2026Apache Tomcat: HTTP/2 trailer header cross-contaminationCVE-2026-80353Oct 20, 2026Apache Tomcat: TOCTOU
Get an email when Apache Tomcat publishes the next one.
See Apache Tomcat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.