![]() ![]() Tomcat Connector is the channel for Tomcat to connect to the outside. The issue was made public on 24 February 2020. This issue was reported to the Apache Tomcat Security Team on 3 January 2020. It is likely that users upgrading to 9.0.31 or later will need to make small changes to their configurations as a result. Users should note that 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 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 or later. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. processing any file in the web application as a JSPįurther, 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.returning arbitrary files from anywhere in the web application including under the WEB-INF and META-INF directories or any other location reachable via ServletContext.getResourceAsStream().This vulnerability report identified a mechanism that allowed the following: bypassing user authentication if Tomcat was configured to trust authentication data provided by the reverse proxy.bypassing security checks based on client IP address.Prior to this vulnerability report, the known risks of an attacker being able to access the AJP port directly were: It was expected (and recommended in the security guide) that this Connector would be disabled if not required. Prior to Tomcat 9.0.31, 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. This was confirmed that it affected all versions of Tomcat 9/8/7/6.ĬVE-2020-1938 || High: AJP Request Injection and potential Remote Code Execution. GhostCat affects all versions of Tomcat in the default configuration. ![]() It was hidden like a ghost into Apache Tomcat for more than a decade. Why is this vulnerability called Ghostcat ? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |