RHSA-2007:0326: Important: tomcat security update
Tomcat is a servlet container for Java Servlet and JavaServer Pagestechnologies.Tomcat was found to accept multiple content-length headers in arequest. This could allow attackers to poison a web-cache, bypass webapplication firewall protection, or conduct cross-site scripting attacks. (CVE-2005-2090)Tomcat permitted various characters as path delimiters. If Tomcat was usedbehind certain proxies and configured to only proxy some contexts, anattacker could construct an HTTP request to work around the contextrestriction and potentially access non-proxied content. (CVE-2007-0450)Several applications distributed in the JSP examples displayed unfilteredvalues. If the JSP examples are accessible, these flaws could allow aremote attacker to perform cross-site scripting attacks. (CVE-2006-7195,CVE-2006-7196)The default Tomcat configuration permitted the use of insecureSSL cipher suites including the anonymous cipher suite. (CVE-2007-1858)Directory listings were enabled by default in Tomcat. Information storedunprotected under the document root was visible to anyone if theadministrator did not disable directory listings. (CVE-2006-3835)Users should upgrade to these erratum packages which contain Tomcat version5.5.23 that resolves these issues. Updated jakarta-commons-modelerpackages are also included which correct a bug when used with Tomcat 5.5.23.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2007:0326?
The severity of RHSA-2007:0326 is classified as important.
How do I fix RHSA-2007:0326?
To fix RHSA-2007:0326, users should apply the recommended updates for their Tomcat version.
What vulnerabilities are associated with RHSA-2007:0326?
RHSA-2007:0326 identifies vulnerabilities that enable attackers to poison web caches and bypass web application firewalls.
Which software is affected by RHSA-2007:0326?
RHSA-2007:0326 affects Apache Tomcat versions that handle multiple content-length headers.
What are the potential risks of not addressing RHSA-2007:0326?
Not addressing RHSA-2007:0326 could lead to exploited vulnerabilities, resulting in data tampering or unauthorized access.