![]() tags | advisory, vulnerability systems | linux, debian advisories | CVE-2023-24998, CVE-2023-41080, CVE-2023-42795, CVE-2023-44487, CVE-2023-45648 SHA-256 | f983a0a85802b2763746bf3bfa97b1786563f79ce2c2bd56f8c915338b5146ae Download | Favorite | View Debian Security Advisory 5521-1 Posted Authored by Debian | Site ĭebian Linux Security Advisory 5521-1 - Several security vulnerabilities have been discovered in the Tomcat servlet and JSP engine. Related Files Debian Security Advisory 5522-1 Posted Authored by Debian | Site ĭebian Linux Security Advisory 5522-1 - Several security vulnerabilities have been discovered in the Tomcat servlet and JSP engine. The vulnerability is limited to the ROOT (default) web application. MLIST: 20200625 svn commit: r1879208 - in /tomcat/site/trunk: docs/security-10.html docs/security-8.html docs/security-9.html xdocs/security-10.xml xdocs/security-8.xml xdocs/security-9.URL Redirection to Untrusted Site ('Open Redirect') vulnerability in FORM authentication feature Apache Tomcat.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M10, from 10.1.0-M1 through 10.0.12, from 9.0.0-M1 through 9.0.79 and from 8.5.0 through 8.5.92. ![]() MLIST: 20200309 Answer file not being used.MLIST: 20200224 CVE-2020-1938 AJP Request Injection and potential Remote Code Execution.MLIST: 20200319 mod_proxy_ajp: patch to set worker secret passed to tomcat.MLIST: 20200831 (GEODE-8471) Dependency security issues in geode-core-1.12.MLIST: 20200528 tomcat8 security update.One thing I have noticed is that when I issue the shutdown.sh for Tomcat, the process still keeps running. MLIST: 20200304 tomcat7 security update Tomcat not Shutting Down Completely (Tomcat 9.0.31) We are in the process of migrating our application from Websphere to Tomcat.MLIST: 20210223 Re: Apache Software Foundation Security Report: 2020.MLIST: 20210125 Apache Software Foundation Security Report: 2020.Note: References are provided for the convenience of the reader to help distinguish between 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 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |