RHSA-2016:2045: Important: tomcat6 security and bug fix update

Published Oct 10, 2016
·
Updated

Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies.Security Fix(es): It was discovered that the Tomcat packages installed certain configuration files read by the Tomcat initialization script as writeable to the tomcat group. A member of the group or a malicious web application deployed on Tomcat could use this flaw to escalate their privileges. (CVE-2016-6325) It was found that several Tomcat session persistence mechanisms could allow a remote, authenticated user to bypass intended SecurityManager restrictions and execute arbitrary code in a privileged context via a web application that placed a crafted object in a session. (CVE-2016-0714) It was discovered that tomcat used the value of the Proxy header from HTTP requests to initialize the HTTPPROXY environment variable for CGI scripts, which in turn was incorrectly used by certain HTTP client implementations to configure the proxy for outgoing HTTP requests. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. (CVE-2016-5388) A directory traversal flaw was found in Tomcat's RequestUtil.java. A remote, authenticated user could use this flaw to bypass intended SecurityManager restrictions and list a parent directory via a '/..' in a pathname used by a web application in a getResource, getResourceAsStream, or getResourcePaths call, as demonstrated by the $CATALINABASE/webapps directory. (CVE-2015-5174) It was found that Tomcat could reveal the presence of a directory even when that directory was protected by a security constraint. A user could make a request to a directory via a URL not ending with a slash and, depending on whether Tomcat redirected that request, could confirm whether that directory existed. (CVE-2015-5345) It was found that Tomcat allowed the StatusManagerServlet to be loaded by a web application when a security manager was configured. This allowed a web application to list all deployed web applications and expose sensitive information such as session IDs. (CVE-2016-0706) Red Hat would like to thank Scott Geary (VendHQ) for reporting CVE-2016-5388. The CVE-2016-6325 issue was discovered by Red Hat Product Security.Bug Fix(es): Due to a bug in the tomcat6 spec file, the catalina.out file's md5sum, size, and mtime attributes were compared to the file's attributes at installation time. Because these attributes change after the service is started, the "rpm -V" command previously failed. With this update, the attributes mentioned above are ignored in the RPM verification and the catalina.out file now passes the verification check. (BZ#1357123)

Affected Software

10 affected componentsFixes available
redhat/tomcat6<6.0.24-98.el6_8
6.0.24-98.el6_8
redhat/tomcat6<6.0.24-98.el6_8
6.0.24-98.el6_8
redhat/tomcat6-admin-webapps<6.0.24-98.el6_8
6.0.24-98.el6_8
redhat/tomcat6-docs-webapp<6.0.24-98.el6_8
6.0.24-98.el6_8
redhat/tomcat6-el<2.1-api-6.0.24-98.el6_8
2.1-api-6.0.24-98.el6_8
redhat/tomcat6-javadoc<6.0.24-98.el6_8
6.0.24-98.el6_8
redhat/tomcat6-jsp<2.1-api-6.0.24-98.el6_8
2.1-api-6.0.24-98.el6_8
redhat/tomcat6-lib<6.0.24-98.el6_8
6.0.24-98.el6_8
redhat/tomcat6-servlet<2.5-api-6.0.24-98.el6_8
2.5-api-6.0.24-98.el6_8
redhat/tomcat6-webapps<6.0.24-98.el6_8
6.0.24-98.el6_8

Remediation

Event History

Oct 10, 2016
Advisory Published
via Red Hat·12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2016:2045?

RHSA-2016:2045 has a medium severity level due to improper file permissions in the Tomcat installation.

2

How do I fix RHSA-2016:2045?

To fix RHSA-2016:2045, update your Tomcat packages to the fixed version 6.0.24-98.el6_8.

3

Which Tomcat versions are affected by RHSA-2016:2045?

The affected version under RHSA-2016:2045 is Tomcat 6 version 6.0.24-98.el6_8 and earlier.

4

What is the impact of RHSA-2016:2045 vulnerability?

The impact of RHSA-2016:2045 can include unauthorized modification of Tomcat configuration files due to incorrect file permissions.

5

Is there a workaround for RHSA-2016:2045 if I cannot update?

A temporary workaround for RHSA-2016:2045 is to manually adjust the permissions of the configuration files to be less permissive.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203