![]() Tomcat has 60% market share of Java Application servers. It can be used to read configs and steal passwords & API tokens - In some cases, it can be used to RCE/write files (think "plant backdoors") with at least 5 POCs already available.īased on this link from 2010, Apache Tomcat has been downloaded 10 Million times. Henry Chen, a security researcher at Alibaba Cloud, published a tweet confirming that exploiting the vulnerability would allow someone to “read any webapps files or include a file to RCE.” Risk ImpactĪccording to a tweet by cyber threat intelligence firm Bad Packets, “mass scanning activity targeting this vulnerability has already begun”. This vulnerability was discovered by a security researcher of Chaitin Tech. The CVSS Base Score is 9.8 (Critical) 1.3 Affected VersionĪpache Tomcat 9.0.30 and prior, Apache Tomcat 8.5.50 and prior and Apache Tomcat 7.0.99 and prior. Watch the video to learn more about this and other important vulnerabilities. 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 few changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. Users wishing to take a defense-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. 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. 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. 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. The Virsec Security Research Lab provides detailed analysis on recent and notable security vulnerabilities. ![]() Virsec Security Research Lab Vulnerability Analysis
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |