Two more important vulnerabilities in Tomcat

Today, two important vulnerabilities have emerged in Tomcat:

CVE-2011-3375 Apache Tomcat Information disclosure

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
-Tomcat 7.0.0 to 7.0.21
-Tomcat 6.0.30 to 6.0.33
-Earlier versions are not affected

Description:
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,
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
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.

Solution:
-Tomcat 7.0.x users should upgrade to 7.0.22 or later.
-Tomcat 6.0.x should be upgraded to 6.0.35 or later.

 

CVE-2012-0022 Apache Tomcat Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
-Tomcat 7.0.0 to 7.0.22
-Tomcat 6.0.0 to 6.0.33
-Tomcat 5.5.0 to 5.5.34
-Earlier, unsupported versions may also be affected

Description:
Analysis of the recent hash collision vulnerability identified unrelated
Inefficiencies with Apache Tomcat's handling of large numbers
Parameters and parameter values. These inefficiencies cocould allow
Attacker, via a specially crafted request, to cause large amounts of CPU
To be used which in turn cocould 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.

Mitigation:
Users of affected versions shocould apply one of the following mitigations:
-Tomcat 7.0.x users shoshould upgrade to 7.0.23 or later
-Tomcat 6.0.x users shoshould upgrade to 6.0.35 or later
-Tomcat 5.5.x users shoshould upgrade to 5.5.35 or later