Questions about Tomcat configuration, and the problems you run into while developing and running applications, will normally be more appropriate on the TOMCAT-USER list instead. This list is reserved for discussions about the development of Tomcat itself. 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. The TOMCAT-DEV mailing list, which you can subscribe to here. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. APACHE TOMCAT 9.0 31 UPGRADEUsers 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. TCD has prerequisites of Apache Ant 1.6.2+ and a Java installation. The download is usually labelled apache-tomcat-9.0.x-deployer. APACHE TOMCAT 9.0 31 CODEThis 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. The TCD is not packaged with the Tomcat core distribution, and must therefore be downloaded separately from the Downloads area. 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. Such a reverse proxy is considered unlikely. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. The updated packages fix security vulnerabilities:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |