ALAS-2017-822

Related Vulnerabilities: CVE-2017-5647   CVE-2017-5648  

Incorrect handling of pipelined requests when send file was usedA bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C. (CVE-2017-5647) Calls to application listeners did not use the appropriate facade objectWhile investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application. (CVE-2017-5648)

ALAS-2017-822


Amazon Linux AMI Security Advisory: ALAS-2017-822
Advisory Release Date: 2017-04-20 06:18 Pacific
Advisory Updated Date: 2017-04-20 21:56 Pacific
Severity: Important

Issue Overview:

Incorrect handling of pipelined requests when send file was used
A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C. (CVE-2017-5647)

Calls to application listeners did not use the appropriate facade object
While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application. (CVE-2017-5648)


Affected Packages:

tomcat7, tomcat8


Issue Correction:
Run yum update tomcat7 to update your system.
Run yum update tomcat8 to update your system.

New Packages:
noarch:
    tomcat7-servlet-3.0-api-7.0.77-1.26.amzn1.noarch
    tomcat7-lib-7.0.77-1.26.amzn1.noarch
    tomcat7-el-2.2-api-7.0.77-1.26.amzn1.noarch
    tomcat7-jsp-2.2-api-7.0.77-1.26.amzn1.noarch
    tomcat7-log4j-7.0.77-1.26.amzn1.noarch
    tomcat7-7.0.77-1.26.amzn1.noarch
    tomcat7-javadoc-7.0.77-1.26.amzn1.noarch
    tomcat7-webapps-7.0.77-1.26.amzn1.noarch
    tomcat7-admin-webapps-7.0.77-1.26.amzn1.noarch
    tomcat7-docs-webapp-7.0.77-1.26.amzn1.noarch
    tomcat8-8.0.43-1.70.amzn1.noarch
    tomcat8-servlet-3.1-api-8.0.43-1.70.amzn1.noarch
    tomcat8-el-3.0-api-8.0.43-1.70.amzn1.noarch
    tomcat8-webapps-8.0.43-1.70.amzn1.noarch
    tomcat8-docs-webapp-8.0.43-1.70.amzn1.noarch
    tomcat8-javadoc-8.0.43-1.70.amzn1.noarch
    tomcat8-jsp-2.3-api-8.0.43-1.70.amzn1.noarch
    tomcat8-log4j-8.0.43-1.70.amzn1.noarch
    tomcat8-admin-webapps-8.0.43-1.70.amzn1.noarch
    tomcat8-lib-8.0.43-1.70.amzn1.noarch

src:
    tomcat7-7.0.77-1.26.amzn1.src
    tomcat8-8.0.43-1.70.amzn1.src