- The following problems were fixed in Apache Tomcat version 6.0.35: <br/><br/> <ul> <li> <strong>Important: Information disclosure CVE-2011-3375</strong><br/> For performance reasons, information parsed from a request is often cached in two places: the internal request object and the internal processor object. These objects are not recycled at exactly the same time. When certain errors occur that needed to be added to the access log, the access logging process triggers the re-population of the request object after it has been recycled. However, the request object was not recycled before being used for the next request. That lead to information leakage (e.g. remote IP address, HTTP headers) from the previous request to the next request. The issue was resolved be ensuring that the request and response objects were recycled after being re-populated to generate the necessary access log entries. This was fixed in revision 1185998.</li> <li> <strong>Important: Authentication bypass and information disclosure CVE-2011-3190</strong><br/> Apache Tomcat supports the AJP protocol which is used with reverse proxies to pass requests and associated data about the request from the reverse proxy to Tomcat. The AJP protocol is designed so that when a request includes a request body, an unsolicited AJP message is sent to Tomcat that includes the first part (or possibly all) of the request body. In certain circumstances, Tomcat did not process this message as a request body but as a new request. This permitted an attacker to have full control over the AJP message permitting authentication bypass and information disclosure. </li> <li> <strong>Important: Denial of service CVE-2012-0022</strong><br/> Analysis of the recent hash collision vulnerability identified unrelated inefficiencies with Apache Tomcat's handling of large numbers of parameters and parameter values. These inefficiencies could allow an attacker, via a specially crafted request, to cause large amounts of CPU to be used which in turn could create a denial of service. The issue was addressed by modifying the Tomcat parameter handling code to efficiently process large numbers of parameters and parameter values. This was fixed in revisions 1200601, 1206324 and 1229027. </li> </ul> <br/><br/><span class="bb-navy">Affected Apache Tomcat versions (6.0.0 - 6.0.33).</span><br/>
- Upgrade to the latest version of Apache Tomcat.