The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.0.0.M21, 8.5.15, 8.0.44, 7.0.78
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected 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, 7.0.0 to 7.0.77
- org.apache.tomcat:tomcatMaven
From 9.0.0.M1 · fixed in 9.0.0.M21
- org.apache.tomcat:tomcatMaven
From 8.5.0 · fixed in 8.5.15
- org.apache.tomcat:tomcatMaven
From 8.0.0 · fixed in 8.0.44
- org.apache.tomcat:tomcatMaven
From 7.0.0 · fixed in 7.0.78
References 25
security.netapp.com
securityfocus.com
oracle.com
access.redhat.com
lists.apache.org
- thread.html/a42c48e37398d76334e17089e43ccab945238b8b7896538478d76066@<announce.tomcat.apache.org>
- thread.html/eb6efa8d59c45a7a9eff94c4b925467d3b3fec8ba7697f3daa314b04@<dev.tomcat.apache.org>
- thread.html/343558d982879bf88ec20dbf707f8c11255f8e219e81d45c4f8d0551@<dev.tomcat.apache.org>
- thread.html/388a323769f1dff84c9ec905455aa73fbcb20338e3c7eb131457f708@<dev.tomcat.apache.org>