Описание
ELSA-2017-0935: tomcat security update (MODERATE)
[0:7.0.69-11]
- Resolves: rhbz#1413591 CVE-2016-8745 tomcat: information disclosure due to incorrect Processor sharing
- Resolves: rhbz#1402662 CVE-2016-6816 tomcat: HTTP Request smuggling vulnerability due to permitting invalid character in HTTP requests
Обновленные пакеты
Oracle Linux 7
Oracle Linux x86_64
tomcat
7.0.69-11.el7_3
tomcat-admin-webapps
7.0.69-11.el7_3
tomcat-docs-webapp
7.0.69-11.el7_3
tomcat-el-2.2-api
7.0.69-11.el7_3
tomcat-javadoc
7.0.69-11.el7_3
tomcat-jsp-2.2-api
7.0.69-11.el7_3
tomcat-jsvc
7.0.69-11.el7_3
tomcat-lib
7.0.69-11.el7_3
tomcat-servlet-3.0-api
7.0.69-11.el7_3
tomcat-webapps
7.0.69-11.el7_3
Связанные CVE
Связанные уязвимости
A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48 resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not not limited to, session ID and the response body. The bug was first noticed in 8.5.x onwards where it appears the refactoring of the Connector code for 8.5.x onwards made it more likely that the bug was observed. Initially it was thought that the 8.5.x refactoring introduced the bug but further investigation has shown that the bug is present in all currently supported Tomcat versions.
A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48 resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not not limited to, session ID and the response body. The bug was first noticed in 8.5.x onwards where it appears the refactoring of the Connector code for 8.5.x onwards made it more likely that the bug was observed. Initially it was thought that the 8.5.x refactoring introduced the bug but further investigation has shown that the bug is present in all currently supported Tomcat versions.