Описание
Security update for tomcat
This update for tomcat to version 9.0.31 fixes the following issues:
Security issues fixed:
- CVE-2019-10072: Fixed a denial-of-service that could have been caused by clients omitting WINDOW_UPDATE messages in HTTP/2 streams (bsc#1139924).
- CVE-2019-12418: Fixed a local privilege escalation by manipulating the RMI registry (bsc#1159723).
- CVE-2019-17563: Fixed a session fixation attack when using FORM authentication (bsc#1159729).
- CVE-2019-17569: Fixed a regression in the handling of Transfer-Encoding headers that would have allowed HTTP Request Smuggling (bsc#1164825).
- CVE-2020-1935: Fixed an HTTP Request Smuggling issue (bsc#1164860).
- CVE-2020-1938: Fixed a file contents disclosure vulnerability (bsc#1164692).
Список пакетов
SUSE Linux Enterprise Server 12 SP4
SUSE Linux Enterprise Server 12 SP5
SUSE Linux Enterprise Server for SAP Applications 12 SP4
SUSE Linux Enterprise Server for SAP Applications 12 SP5
Ссылки
- Link for SUSE-SU-2020:0632-1
- E-Mail link for SUSE-SU-2020:0632-1
- SUSE Security Ratings
- SUSE Bug 1139924
- SUSE Bug 1159723
- SUSE Bug 1159729
- SUSE Bug 1164692
- SUSE Bug 1164825
- SUSE Bug 1164860
- SUSE CVE CVE-2019-10072 page
- SUSE CVE CVE-2019-12418 page
- SUSE CVE CVE-2019-17563 page
- SUSE CVE CVE-2019-17569 page
- SUSE CVE CVE-2020-1935 page
- SUSE CVE CVE-2020-1938 page
Описание
The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
Затронутые продукты
Ссылки
- CVE-2019-10072
- SUSE Bug 1139924
- SUSE Bug 1154162
Описание
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.
Затронутые продукты
Ссылки
- CVE-2019-12418
- SUSE Bug 1159723
Описание
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.
Затронутые продукты
Ссылки
- CVE-2019-17563
- SUSE Bug 1159729
Описание
The refactoring present in Apache Tomcat 9.0.28 to 9.0.30, 8.5.48 to 8.5.50 and 7.0.98 to 7.0.99 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
Затронутые продукты
Ссылки
- CVE-2019-17569
- SUSE Bug 1164825
- SUSE Bug 1165858
Описание
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
Затронутые продукты
Ссылки
- CVE-2020-1935
- SUSE Bug 1164860
Описание
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, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. 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. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. 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.
Затронутые продукты
Ссылки
- CVE-2020-1938
- SUSE Bug 1164692
- SUSE Bug 1166559
- SUSE Bug 1169066
- SUSE Bug 1175170