CVE-2017-5664 Improper Handling of Exceptional Conditions in Apache Tomcat

High 7.5 Published Updated

Attackers can modify or delete static error pages by sending non-GET requests, if the Default Servlet is configured to permit writes.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

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.

PackageAffectedFixed in
org.apache.tomcat:tomcat MavenFrom 7.0.07.0.78
org.apache.tomcat:tomcat MavenFrom 7.0.07.0.78
org.apache.tomcat:tomcat MavenFrom 8.0.08.0.44
org.apache.tomcat:tomcat MavenFrom 8.0.08.0.44
org.apache.tomcat:tomcat MavenFrom 8.5.08.5.15
org.apache.tomcat:tomcat MavenFrom 8.5.08.5.15
2 more packages
org.apache.tomcat:tomcat MavenFrom 9.0.0.M19.0.0.M21
org.apache.tomcat:tomcat MavenFrom 9.0.0.M19.0.0.M21

Products include 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.

All Apache Tomcat vulnerabilities

Sources

Also known as DLA-996-1, DSA-3891-1, DSA-3892-1, GHSA-jmvv-524f-hj5j, MGASA-2017-0196, UBUNTU-CVE-2017-5664.

Is CVE-2017-5664 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free