Apache Tomcat 7.x through 7.0.70 and 8.x through 8.5.4, when the CGI Servlet is enabled, follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an applications outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an httpoxy issue. NOTE: the vendor states A mitigation is planned for future releases of Tomcat, tracked as CVE-2016-5388; in other words, this is not a CVE ID for a vulnerability.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Enterprise_linux_desktop | Redhat | 7.0 (including) | 7.0 (including) |
| Enterprise_linux_hpc_node | Redhat | 7.0 (including) | 7.0 (including) |
| Enterprise_linux_hpc_node_eus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_server | Redhat | 7.0 (including) | 7.0 (including) |
| Enterprise_linux_server_aus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_server_eus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_server_tus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_workstation | Redhat | 7.0 (including) | 7.0 (including) |
| Red Hat Enterprise Linux 6 | RedHat | tomcat6-0:6.0.24-98.el6_8 | * |
| Red Hat Enterprise Linux 7 | RedHat | tomcat-0:7.0.54-8.el7_2 | * |
| Red Hat JBoss Web Server 3.0 | RedHat | * | |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | httpd24-0:2.4.6-62.ep7.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | tomcat7-0:7.0.59-51_patch_01.ep7.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | tomcat8-0:8.0.18-62_patch_01.ep7.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | httpd24-0:2.4.6-62.ep7.el7 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | tomcat7-0:7.0.59-51_patch_01.ep7.el7 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | tomcat8-0:8.0.18-62_patch_01.ep7.el7 | * |
| Tomcat6 | Ubuntu | esm-apps/xenial | * |
| Tomcat6 | Ubuntu | esm-infra-legacy/trusty | * |
| Tomcat6 | Ubuntu | precise | * |
| Tomcat6 | Ubuntu | trusty | * |
| Tomcat6 | Ubuntu | trusty/esm | * |
| Tomcat6 | Ubuntu | wily | * |
| Tomcat6 | Ubuntu | xenial | * |
| Tomcat7 | Ubuntu | artful | * |
| Tomcat7 | Ubuntu | bionic | * |
| Tomcat7 | Ubuntu | cosmic | * |
| Tomcat7 | Ubuntu | esm-apps/bionic | * |
| Tomcat7 | Ubuntu | esm-apps/xenial | * |
| Tomcat7 | Ubuntu | precise | * |
| Tomcat7 | Ubuntu | trusty | * |
| Tomcat7 | Ubuntu | upstream | * |
| Tomcat7 | Ubuntu | wily | * |
| Tomcat7 | Ubuntu | xenial | * |
| Tomcat7 | Ubuntu | yakkety | * |
| Tomcat7 | Ubuntu | zesty | * |
| Tomcat8 | Ubuntu | upstream | * |
| Tomcat8 | Ubuntu | wily | * |
| Tomcat8 | Ubuntu | xenial | * |
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: