CVE-2017-5664
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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Apache | Tomcat | 7.0.0 | — |
| Apache | Tomcat | 7.0.1 | — |
| Apache | Tomcat | 7.0.2 | — |
| Apache | Tomcat | 7.0.3 | — |
| Apache | Tomcat | 7.0.4 | — |
| Apache | Tomcat | 7.0.5 | — |
| Apache | Tomcat | 7.0.6 | — |
| Apache | Tomcat | 7.0.7 | — |
| Apache | Tomcat | 7.0.8 | — |
| Apache | Tomcat | 7.0.9 | — |
| Apache | Tomcat | 7.0.10 | — |
| Apache | Tomcat | 7.0.11 | — |
| Apache | Tomcat | 7.0.12 | — |
| Apache | Tomcat | 7.0.13 | — |
| Apache | Tomcat | 7.0.14 | — |
| Apache | Tomcat | 7.0.15 | — |
| Apache | Tomcat | 7.0.16 | — |
| Apache | Tomcat | 7.0.17 | — |
| Apache | Tomcat | 7.0.18 | — |
| Apache | Tomcat | 7.0.19 | — |
| Apache | Tomcat | 7.0.20 | — |
| Apache | Tomcat | 7.0.21 | — |
| Apache | Tomcat | 7.0.22 | — |
| Apache | Tomcat | 7.0.23 | — |
| Apache | Tomcat | 7.0.24 | — |
| Apache | Tomcat | 7.0.25 | — |
| Apache | Tomcat | 7.0.26 | — |
| Apache | Tomcat | 7.0.27 | — |
| Apache | Tomcat | 7.0.28 | — |
| Apache | Tomcat | 7.0.29 | — |
| Apache | Tomcat | 7.0.30 | — |
| Apache | Tomcat | 7.0.31 | — |
| Apache | Tomcat | 7.0.32 | — |
| Apache | Tomcat | 7.0.33 | — |
| Apache | Tomcat | 7.0.34 | — |
| Apache | Tomcat | 7.0.35 | — |
| Apache | Tomcat | 7.0.36 | — |
| Apache | Tomcat | 7.0.37 | — |
| Apache | Tomcat | 7.0.38 | — |
| Apache | Tomcat | 7.0.39 | — |
| Apache | Tomcat | 7.0.40 | — |
| Apache | Tomcat | 7.0.41 | — |
| Apache | Tomcat | 7.0.42 | — |
| Apache | Tomcat | 7.0.43 | — |
| Apache | Tomcat | 7.0.44 | — |
| Apache | Tomcat | 7.0.45 | — |
| Apache | Tomcat | 7.0.46 | — |
| Apache | Tomcat | 7.0.47 | — |
| Apache | Tomcat | 7.0.48 | — |
| Apache | Tomcat | 7.0.49 | — |
Showing 50 of 135 affected configurations. See NVD for the full list.
References
- http://www.securityfocus.com/bid/98888Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/98888Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5664?
How severe is CVE-2017-5664?
How do I fix CVE-2017-5664?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-5658The statistics generator in Apache Pony Mail 0.7 to 0.9 was …
- CVE-2017-5659Apache Traffic Server before 6.2.1 generates a coredump when…
- CVE-2017-5660There is a vulnerability in Apache Traffic Server (ATS) 6.2.…
- CVE-2017-5661In Apache FOP before 2.2, files lying on the filesystem of t…
- CVE-2017-5662In Apache Batik before 1.9, files lying on the filesystem of…
- CVE-2017-5663In Apache Fineract 0.4.0-incubating, 0.5.0-incubating, and 0…
- CVE-2017-5665The splt_cue_export_to_file function in cue.c in libmp3splt …
- CVE-2017-5666The free_options function in options_manager.c in mp3splt 2.…
- CVE-2017-5667The sdhci_sdma_transfer_multi_blocks function in hw/sd/sdhci…6.5
- CVE-2017-5668bitlbee-libpurple before 3.5.1 allows remote attackers to ca…
- CVE-2017-5669The do_shmat function in ipc/shm.c in the Linux kernel throu…7.8
- CVE-2017-5670Riverbed RiOS through 9.6.0 deletes the secure vault with th…
Are you affected by CVE-2017-5664?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST