Описание
ELSA-2020-0855: tomcat security update (IMPORTANT)
[0:7.0.76-11]
- Resolves: rhbz#1806801 CVE-2020-1938 tomcat: Apache Tomcat AJP File Read/Inclusion Vulnerability
Обновленные пакеты
Oracle Linux 7
Oracle Linux aarch64
tomcat
7.0.76-11.el7_7
tomcat-admin-webapps
7.0.76-11.el7_7
tomcat-docs-webapp
7.0.76-11.el7_7
tomcat-el-2.2-api
7.0.76-11.el7_7
tomcat-javadoc
7.0.76-11.el7_7
tomcat-jsp-2.2-api
7.0.76-11.el7_7
tomcat-jsvc
7.0.76-11.el7_7
tomcat-lib
7.0.76-11.el7_7
tomcat-servlet-3.0-api
7.0.76-11.el7_7
tomcat-webapps
7.0.76-11.el7_7
Oracle Linux x86_64
tomcat
7.0.76-11.el7_7
tomcat-admin-webapps
7.0.76-11.el7_7
tomcat-docs-webapp
7.0.76-11.el7_7
tomcat-el-2.2-api
7.0.76-11.el7_7
tomcat-javadoc
7.0.76-11.el7_7
tomcat-jsp-2.2-api
7.0.76-11.el7_7
tomcat-jsvc
7.0.76-11.el7_7
tomcat-lib
7.0.76-11.el7_7
tomcat-servlet-3.0-api
7.0.76-11.el7_7
tomcat-webapps
7.0.76-11.el7_7
Связанные CVE
Связанные уязвимости
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. 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. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. 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, a...
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. 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. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. 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, a...
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. 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. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. 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, alon
When using the Apache JServ Protocol (AJP), care must be taken when tr ...
