For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.ĬVE (at NVD CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/ CVE, GitHub advisories/ code/ issues, web search, more) This could result in responses appearing to be sent for the wrong request. Custom Servlets used as error pages must ensure that they handle any error dispatch as a GET request, regardless of the actual method.A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. (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. 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. This means that the request is presented to the error page with the original HTTP method. 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. CVSS 3.0 Base Score 5.9 (Integrity impacts). This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE, Java SE Embedded accessible data. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Supported versions that are affected are Java SE: 7u211, 8u202, 11.0.2 and 12 Java SE Embedded: 8u201. Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: RMI). It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. If such connections are available to an attacker, they can be exploited in ways that may be surprising. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |