CVE-2017-5664
Improper Handling of Exceptional Conditions in Apache Tomcat
Reported by apache · Published 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 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.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | 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 |
| Apache Software Foundation | Apache Tomcat | 7.0.0, 8.0.0.RC1, 8.5.0 |
| Maven | org.apache.tomcat:tomcat | 7.0.0, 8.0.0, 8.5.0 |
| Maven | org.apache.tomcat.embed:tomcat-embed-core | 8.5.0, 9.0.0, 8.0.9 |
Timeline
- Jun 6, 2017 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Sep 8, 2025 CVE Updated
- Mar 6, 2026 Distribution Patch (16 in total, the first dated here)
- Mar 6, 2026 Security Advisory (16 in total, the first dated here)
- Sep 28, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2017-5664
vulnetix vdb fixes CVE-2017-5664
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-5664/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- DSA-3891 vendor-advisoryx_refsource_DEBIAN
- x_refsource_CONFIRM
- 98888 vdb-entryx_refsource_BID
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- RHSA-2017:3080 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- RHSA-2017:1801 vendor-advisoryx_refsource_REDHAT
- RHSA-2017:2635 vendor-advisoryx_refsource_REDHAT
- RHSA-2017:2638 vendor-advisoryx_refsource_REDHAT
- RHSA-2017:2494 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- [tomcat-users] 20170606 [SECURITY] CVE-2017-5664 Apache Tomcat Security Constraint Bypass mailing-listx_refsource_MLIST
- RHSA-2017:2636 vendor-advisoryx_refsource_REDHAT
- RHSA-2017:1809 vendor-advisoryx_refsource_REDHAT
- RHSA-2017:2637 vendor-advisoryx_refsource_REDHAT
- 1038641 vdb-entryx_refsource_SECTRACK
- DSA-3892 vendor-advisoryx_refsource_DEBIAN
- RHSA-2017:2633 vendor-advisoryx_refsource_REDHAT
…and 35 more