# CVE-2017-5664: Improper Handling of Exceptional Conditions in Apache Tomcat > Attackers can modify or delete static error pages by sending non-GET requests, if the Default Servlet is configured to permit writes. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jun 2017 - **Updated:** 15 Oct 2026 - **Also known as:** DLA-996-1, DSA-3891-1, DSA-3892-1, GHSA-jmvv-524f-hj5j, MGASA-2017-0196, UBUNTU-CVE-2017-5664 ## What is CVE-2017-5664? CVE-2017-5664 is a high-severity vulnerability in Apache Tomcat, published on 6 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-755 (Improper Handling of Exceptional Conditions) ## Which versions are affected by CVE-2017-5664? 8 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.78 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.78 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0 | 8.0.44 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0 | 8.0.44 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.15 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.15 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M21 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M21 | Products: Apache Tomcat. ## How do I fix CVE-2017-5664? Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 7.0.78, 8.0.44, 8.5.15 or 9.0.0.M21. ## Is CVE-2017-5664 being exploited? There is no known exploitation of CVE-2017-5664 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-5664 and fix it if it is affected. What it is: CVE-2017-5664 is a high-severity vulnerability in Apache Tomcat, published on 6 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-5664 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.78 - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.78 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0; fixed in 8.0.44 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0; fixed in 8.0.44 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.15 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.15 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M21 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M21 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-5664/ (Markdown: https://insights.sbomify.com/CVE-2017-5664/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5664 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5664 - OSV: https://osv.dev/vulnerability/CVE-2017-5664 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-5664/ Summaries are generated and may contain mistakes; the official description above is the record.