The Expression Language (EL) implementation in Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.58, and 8.x before 8.0.16 does not properly consider the possibility of an accessible interface implemented by an inaccessible class, which allows attackers to bypass a SecurityManager protection mechanism via a web application that leverages use of incorrect privileges during EL evaluation.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Debian_linux | Debian | 7.0 (including) | 7.0 (including) |
| Red Hat Enterprise Linux 6 | RedHat | tomcat6-0:6.0.24-94.el6_7 | * |
| Red Hat Enterprise Linux 7 | RedHat | tomcat-0:7.0.54-8.el7_2 | * |
| Red Hat JBoss Enterprise Web Server 2 for RHEL 5 | RedHat | tomcat6-0:6.0.41-15_patch_04.ep6.el5 | * |
| Red Hat JBoss Enterprise Web Server 2 for RHEL 5 | RedHat | tomcat7-0:7.0.54-19_patch_04.ep6.el5 | * |
| Red Hat JBoss Enterprise Web Server 2 for RHEL 6 | RedHat | tomcat6-0:6.0.41-15_patch_04.ep6.el6 | * |
| Red Hat JBoss Enterprise Web Server 2 for RHEL 6 | RedHat | tomcat7-0:7.0.54-19_patch_04.ep6.el6 | * |
| Red Hat JBoss Enterprise Web Server 2 for RHEL 7 | RedHat | tomcat6-0:6.0.41-15_patch_04.ep6.el7 | * |
| Red Hat JBoss Enterprise Web Server 2 for RHEL 7 | RedHat | tomcat7-0:7.0.54-20_patch_04.ep6.el7 | * |
| Red Hat JBoss Web Server 2.1 | RedHat | * | |
| Tomcat6 | Ubuntu | precise | * |
| Tomcat6 | Ubuntu | trusty | * |
| Tomcat6 | Ubuntu | upstream | * |
| Tomcat6 | Ubuntu | utopic | * |
| Tomcat6 | Ubuntu | vivid | * |
| Tomcat6 | Ubuntu | wily | * |
| Tomcat6 | Ubuntu | xenial | * |
| Tomcat7 | Ubuntu | precise | * |
| Tomcat7 | Ubuntu | trusty | * |
| Tomcat7 | Ubuntu | upstream | * |
| Tomcat7 | Ubuntu | utopic | * |
| Tomcat7 | Ubuntu | vivid | * |
| Tomcat8 | Ubuntu | upstream | * |
| Tomcat8 | Ubuntu | utopic | * |
| Tomcat8 | Ubuntu | vivid | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: