APACHE TOMCAT 7.0.88 EXPLOIT UPGRADE

A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration.

APACHE TOMCAT 7.0.88 EXPLOIT UPGRADE

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 Vulnerabilities and exploits of Apache Tomcat 8.5.0 Apache Tomcat 8.5.1 Apache Tomcat 8.5.2 Apache Tomcat 8.5.3 Apache Tomcat 8.5.4 Apache Tomcat 8.5.5.

Apache tomcat 7.0.88 exploit