Moderate CentOS tomcat Security Update


tomcat-7.0.69-11.el7_3.noarch.rpm, tomcat-7.0.69-11.el7_3.src.rpm, tomcat-admin-webapps-7.0.69-11.el7_3.noarch.rpm, tomcat-docs-webapp-7.0.69-11.el7_3.noarch.rpm, tomcat-el-2.2-api-7.0.69-11.el7_3.noarch.rpm, tomcat-javadoc-7.0.69-11.el7_3.noarch.rpm, tomcat-jsp-2.2-api-7.0.69-11.el7_3.noarch.rpm, tomcat-jsvc-7.0.69-11.el7_3.noarch.rpm, tomcat-lib-7.0.69-11.el7_3.noarch.rpm, tomcat-servlet-3.0-api-7.0.69-11.el7_3.noarch.rpm, tomcat-webapps-7.0.69-11.el7_3.noarch.rpm,
2018-01-18 11:14
2017-07-27 19:13
2017-07-27 18:03
2017-07-27 00:03
2017-07-26 23:03
2017-07-26 22:03
2017-04-14 09:03


An update for tomcat is now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies.

Security Fix(es):

* It was discovered that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other then their own. (CVE-2016-6816)

Note: This fix causes Tomcat to respond with an HTTP 400 Bad Request error when request contains characters that are not permitted by the HTTP specification to appear not encoded, even though they were previously accepted. The newly introduced system property tomcat.util.http.parser.HttpParser.requestTargetAllow can be used to configure Tomcat to accept curly braces ({ and }) and the pipe symbol (|) in not encoded form, as these are often used in URLs without being properly encoded.

* A bug was discovered in the error handling of the send file code for the NIO HTTP connector. This led to the current Processor object being added to the Processor cache multiple times allowing information leakage between requests including, and not limited to, session ID and the response body. (CVE-2016-8745)
Please see

Am I vulnerable?

The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.

Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.

Sign up for monitoring

Affected package information

Release Package Patched in
7 tomcat tomcat-7.0.69-11.el7_3.noarch.rpm
tomcat tomcat-7.0.69-11.el7_3.src.rpm
tomcat-admin-webapps tomcat-admin-webapps-7.0.69-11.el7_3.noarch.rpm
tomcat-docs-webapp tomcat-docs-webapp-7.0.69-11.el7_3.noarch.rpm
tomcat-el-2.2-api tomcat-el-2.2-api-7.0.69-11.el7_3.noarch.rpm
tomcat-javadoc tomcat-javadoc-7.0.69-11.el7_3.noarch.rpm
tomcat-jsp-2.2-api tomcat-jsp-2.2-api-7.0.69-11.el7_3.noarch.rpm
tomcat-jsvc tomcat-jsvc-7.0.69-11.el7_3.noarch.rpm
tomcat-lib tomcat-lib-7.0.69-11.el7_3.noarch.rpm
tomcat-servlet-3.0-api tomcat-servlet-3.0-api-7.0.69-11.el7_3.noarch.rpm
tomcat-webapps tomcat-webapps-7.0.69-11.el7_3.noarch.rpm