logo
DATABASE RESOURCES PRICING ABOUT US

Fixed in Apache Tomcat 6.0.47

Description

_Note: The issues below were fixed in Apache Tomcat 6.0.46 but the release vote for the 6.0.46 release candidate did not pass. Therefore, although users must download 6.0.47 to obtain a version that includes fixes for these issues, version 6.0.46 is not included in the list of affected versions._ **Low: Unrestricted Access to Global Resources** [CVE-2016-6797](<https://vulners.com/cve/CVE-2016-6797>) The ResourceLinkFactory 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. This was fixed in revision [1757285](<https://svn.apache.org/viewvc?view=rev&rev=1757285>). This issue was identified by the Apache Tomcat Security Team on 18 January 2016 and made public on 27 October 2016. Affects: 6.0.0 to 6.0.45 **Low: Security Manager Bypass** [CVE-2016-6796](<https://vulners.com/cve/CVE-2016-6796>) A malicious web application was able to bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet. This was fixed in revisions [1758496](<https://svn.apache.org/viewvc?view=rev&rev=1758496>) and [1763237](<https://svn.apache.org/viewvc?view=rev&rev=1763237>). This issue was identified by the Apache Tomcat Security Team on 27 December 2015 and made public on 27 October 2016. Affects: 6.0.0 to 6.0.45 **Low: System Property Disclosure** [CVE-2016-6794](<https://vulners.com/cve/CVE-2016-6794>) When a SecurityManager is configured, a web application's ability to read system properties should be controlled by the SecurityManager. Tomcat's 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. This was fixed in revision [1754733](<https://svn.apache.org/viewvc?view=rev&rev=1754733>). This issue was identified by the Apache Tomcat Security Team on 27 December 2015 and made public on 27 October 2016. Affects: 6.0.0 to 6.0.45 **Low: Security Manager Bypass** [CVE-2016-5018](<https://vulners.com/cve/CVE-2016-5018>) A malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications. This was fixed in revisions [1754904](<https://svn.apache.org/viewvc?view=rev&rev=1754904>) and [1761718](<https://svn.apache.org/viewvc?view=rev&rev=1761718>). This issue was discovered by Alvaro Munoz and Alexander Mirosh of the HP Enterprise Security Team and reported to the Apache Tomcat Security Team on 5 July 2016. It was made public on 27 October 2016. Affects: 6.0.0 to 6.0.45 **Low: Timing Attack** [CVE-2016-0762](<https://vulners.com/cve/CVE-2016-0762>) The Realm implementations 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. This was fixed in revision [1758506](<https://svn.apache.org/viewvc?view=rev&rev=1758506>). This issue was identified by the Apache Tomcat Security Team on 1 January 2016 and made public on 27 October 2016. Affects: 6.0.0 to 6.0.45


Affected Software


CPE Name Name Version
apache tomcat 6.0.0
apache tomcat 6.0.45

Related