Custom Servlets used as error pages 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. JSPs used as error pages must must ensure that they handle any error dispatch as a GET request, regardless of the actual method. Notes for other user provided error pages: (1) Unless explicitly coded otherwise, JSPs ignore the HTTP method. 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. The session-persistence implementation in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0. 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. According to its self-reported version number. This means that the request is presented to the error page with the original HTTP method. The remote Apache Tomcat server is affected by an information disclosure vulnerability. 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. :tomcat-catalina is a Tomcat Servlet Engine Core Classes and Standard implementations.Īffected versions of this package are vulnerable to Access Restriction Bypass. Apache Tomcat 7.0.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |