![]() Tomcat6-javadoc is signed with Red Hat redhatrelease2 key Tomcat6-el-2.1-api is signed with Red Hat redhatrelease2 key Tomcat6-docs-webapp is signed with Red Hat redhatrelease2 key Tomcat6-admin-webapps is signed with Red Hat redhatrelease2 key Tomcat6 is signed with Red Hat redhatrelease2 key Red Hat Enterprise Linux must be installed This can result in a number of unwanted outcomes, including remote code execution.ĬVE-2020-9484 tomcat: deserialization flaw in session persistence storage leading to RCE ![]() By injecting a malformed object into a vulnerable application, an adversary can potentially compromise the application by manipulating the deserialization process. These objects are then deserialized when needed to recover the data/state. Developers leverage serialization in order to convert data or state into a static, binary format for saving to disk or transferring over a network. 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.An adversary attempts to exploit an application by injecting additional, malicious content during its processing of serialized objects. 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. A successful attack can lead to local file inclusion. This signature detects attempts to exploit a known vulnerability against Apache Tomcat. Apache Tomcat AJP Connector Local File Inclusion
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |