Apache Tomcat version older than 6.0.36

Description
  • The following problems were fixed in Apache Tomcat version 6.0.36: <br/><br/> <ul> <li> <strong>Important: Denial of service CVE-2012-2733</strong><br/> The checks that limited the permitted size of request headers were implemented too late in the request parsing process for the HTTP NIO connector. This enabled a malicious user to trigger an OutOfMemoryError by sending a single request with very large headers. This was fixed in revision 1356208. </li> <li> <strong>DIGEST authentication weakness CVE-2012-3439</strong><br/> Three weaknesses in Tomcat's implementation of DIGEST authentication were identified and resolved:<br/> Tomcat tracked client rather than server nonces and nonce count.<br/> When a session ID was present, authentication was bypassed.<br/> The user name and password were not checked before when indicating that a nonce was stale.<br/> These issues reduced the security of DIGEST authentication making replay attacks possible in some circumstances. </li> <li> <strong>Important: Bypass of security constraints CVE-2012-3546</strong><br/> When using FORM authentication it was possible to bypass the security constraint checks in the FORM authenticator by appending /j_security_check to the end of the URL if some other component (such as the Single-Sign-On valve) had called request.setUserPrincipal() before the call to FormAuthenticator#authenticate(). This was fixed in revision 1381035. </li> <li> <strong>Important: Bypass of CSRF prevention filter CVE-2012-4431</strong><br/> The CSRF prevention filter could be bypassed if a request was made to a protected resource without a session identifier present in the request. This was fixed in revision 1394456. </li> <li> <strong>Important: Denial of service CVE-2012-4534</strong><br/> When using the NIO connector with sendfile and HTTPS enabled, if a client breaks the connection while reading the response an infinite loop is entered leading to a denial of service. This was originally reported as bug 52858. This was fixed in revision 1372035. </li> </ul> <br/><br/><span class="bb-navy">Affected Apache Tomcat versions (6.0.0 - 6.0.36).</span><br/>
Remediation
  • Upgrade to the latest version of Apache Tomcat.
References