tomcat-7.0.76-2.el7

Tomcat is the servlet container that is used in the official Reference
Implementation for the Java Servlet and JavaServer Pages technologies.
The Java Servlet and JavaServer Pages specifications are developed by
Sun under the Java Community Process.

Tomcat is developed in an open and participatory environment and
released under the Apache Software License version 2.0. Tomcat is intended
to be a collaboration of the best-of-breed developers from around the world.

CVE-2016-0762
The Realm implementations in Apache Tomcat versions 9.0.0.M1 to
9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and
6.0.0 to 6.0.45 did not process the supplied password if the supplied
user name did not exist. This made a timing attack possible to
determine valid user names. Note that the default configuration
includes the LockOutRealm which makes exploitation of this
vulnerability harder.
CVE-2016-5018
In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to
8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web
application was able to bypass a configured SecurityManager via a
Tomcat utility method that was accessible to web applications.
CVE-2016-6794
When a SecurityManager is configured, a web application's ability to
read system properties should be controlled by the SecurityManager. In
Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to
8.0.36, 7.0.0 to 7.0.70, 6.0.0 to 6.0.45 the system property
replacement feature for configuration files could be used by a
malicious web application to bypass the SecurityManager and read
system properties that should not be visible.
CVE-2016-6796
A malicious web application running on Apache Tomcat 9.0.0.M1 to
9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and
6.0.0 to 6.0.45 was able to bypass a configured SecurityManager via
manipulation of the configuration parameters for the JSP Servlet.
CVE-2016-6797
The ResourceLinkFactory implementation in Apache Tomcat 9.0.0.M1 to
9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and
6.0.0 to 6.0.45 did not limit web application access to global JNDI
resources to those resources explicitly linked to the web application.
Therefore, it was possible for a web application to access any global
JNDI resource whether an explicit ResourceLink had been configured or
not.