RHSA-2007:0326High

Red Hat Security Advisory: tomcat security update

Published
May 21, 2007
Last Modified
January 6, 2026

🔗 CVE IDs covered (7)

CVE-2005-2090 →CVE-2006-3835 →CVE-2006-7195 →CVE-2006-7196 →CVE-2007-0450 →CVE-2007-1358 →CVE-2007-1858 →

📋 Description

CVE-2005-2090 — tomcat multiple content-length header poisioning CVE-2006-3835 — tomcat directory listing issue CVE-2006-7195 — tomcat XSS in example webapps CVE-2006-7196 — tomcat XSS in example webapps CVE-2007-0450 — tomcat directory traversal CVE-2007-1358 — tomcat accept-language xss flaw CVE-2007-1858 — tomcat anonymous cipher issue

🎯 Affected products48

  • Red Hat Application Server v2 4AS
  • Red Hat Application Server v2 4ES
  • Red Hat Application Server v2 4WS
  • jakarta-commons-modeler-0:2.0-3jpp_2rh.noarch as a component of Red Hat Application Server v2 4AS
  • jakarta-commons-modeler-0:2.0-3jpp_2rh.noarch as a component of Red Hat Application Server v2 4ES
  • jakarta-commons-modeler-0:2.0-3jpp_2rh.noarch as a component of Red Hat Application Server v2 4WS
  • jakarta-commons-modeler-0:2.0-3jpp_2rh.src as a component of Red Hat Application Server v2 4AS
  • jakarta-commons-modeler-0:2.0-3jpp_2rh.src as a component of Red Hat Application Server v2 4ES
  • jakarta-commons-modeler-0:2.0-3jpp_2rh.src as a component of Red Hat Application Server v2 4WS
  • jakarta-commons-modeler-javadoc-0:2.0-3jpp_2rh.noarch as a component of Red Hat Application Server v2 4AS
  • jakarta-commons-modeler-javadoc-0:2.0-3jpp_2rh.noarch as a component of Red Hat Application Server v2 4ES
  • jakarta-commons-modeler-javadoc-0:2.0-3jpp_2rh.noarch as a component of Red Hat Application Server v2 4WS
  • tomcat5-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4AS
  • tomcat5-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4ES
  • tomcat5-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4WS
  • tomcat5-0:5.5.23-0jpp_4rh.3.src as a component of Red Hat Application Server v2 4AS
  • tomcat5-0:5.5.23-0jpp_4rh.3.src as a component of Red Hat Application Server v2 4ES
  • tomcat5-0:5.5.23-0jpp_4rh.3.src as a component of Red Hat Application Server v2 4WS
  • tomcat5-admin-webapps-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4AS
  • tomcat5-admin-webapps-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4ES
  • tomcat5-admin-webapps-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4WS
  • tomcat5-common-lib-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4AS
  • tomcat5-common-lib-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4ES
  • tomcat5-common-lib-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4WS
  • tomcat5-jasper-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4AS
  • tomcat5-jasper-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4ES
  • tomcat5-jasper-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4WS
  • tomcat5-jasper-javadoc-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4AS
  • tomcat5-jasper-javadoc-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4ES
  • tomcat5-jasper-javadoc-0:5.5.23-0jpp_4rh.3.noarch as a component of Red Hat Application Server v2 4WS
  • +18 more not shown

✅ Remediation

Note: /etc/tomcat5/web.xml has been updated to disable directory listing by default. If you have previously modified /etc/tomcat5/web.xml, this change will not be made automatically and you should manually update the value for the "listings" parameter to "false". Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system.

🔗 References (5)