RHSA-2016:2046: Important: tomcat security 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 configuration file /usr/lib/tmpfiles.d/tomcat.conf 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-5425) 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 the expression language resolver evaluated expressions within a privileged code section. A malicious web application could use this flaw to bypass security manager protections. (CVE-2014-7810) 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 session fixation flaw was found in the way Tomcat recycled the requestedSessionSSL field. If at least one web application was configured to use the SSL session ID as the HTTP session ID, an attacker could reuse a previously used session ID for further requests. (CVE-2015-5346) Red Hat would like to thank Dawid Golunski (http://legalhackers.com) for reporting CVE-2016-5425 and Scott Geary (VendHQ) for reporting CVE-2016-5388. The CVE-2016-6325 issue was discovered by Red Hat Product Security.

Affected Software

11 affected componentsFixes available
redhat/tomcat<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat-admin-webapps<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat-docs-webapp<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat-el<2.2-api-7.0.54-8.el7_2
2.2-api-7.0.54-8.el7_2
redhat/tomcat-javadoc<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat-jsp<2.2-api-7.0.54-8.el7_2
2.2-api-7.0.54-8.el7_2
redhat/tomcat-jsvc<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat-lib<7.0.54-8.el7_2
7.0.54-8.el7_2
redhat/tomcat-servlet<3.0-api-7.0.54-8.el7_2
3.0-api-7.0.54-8.el7_2
redhat/tomcat-webapps<7.0.54-8.el7_2
7.0.54-8.el7_2

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:2046?

The severity of RHSA-2016:2046 is typically classified as moderate due to the writeable configuration file vulnerability that could allow unauthorized changes.

2

How do I fix RHSA-2016:2046?

To fix RHSA-2016:2046, ensure that the file /usr/lib/tmpfiles.d/tomcat.conf is not writable by the tomcat group.

3

What versions of Tomcat are affected by RHSA-2016:2046?

RHSA-2016:2046 affects Apache Tomcat versions up to and including 7.0.54-8.el7_2.

4

What are the consequences of ignoring RHSA-2016:2046?

Ignoring RHSA-2016:2046 could lead to unauthorized modifications to the Tomcat configuration, potentially compromising the application security.

5

Is there a patch available for RHSA-2016:2046?

Yes, a patch is available that updates the affected packages to resolve the vulnerability identified in RHSA-2016:2046.

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