RHSA-2017:0527: Moderate: tomcat6 security update
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)
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2017:0527?
The severity of RHSA-2017:0527 is classified as moderate.
How do I fix RHSA-2017:0527?
To fix RHSA-2017:0527, update your Apache Tomcat to version 6.0.24-105.el6_8 or later.
What vulnerabilities does RHSA-2017:0527 address?
RHSA-2017:0527 addresses vulnerabilities related to improper parsing of the HTTP request line.
Which versions of Apache Tomcat are affected by RHSA-2017:0527?
Apache Tomcat versions prior to 6.0.24-105.el6_8 are affected by RHSA-2017:0527.
Where can I find more information about RHSA-2017:0527?
More information about RHSA-2017:0527 can typically be found within your system's package management system or security advisories.