Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 if JmxRemoteLifecycleListener is used and an attacker can reach JMX ports. The issue exists because this listener wasnt updated for consistency with the CVE-2016-3427 Oracle patch that affected credential types.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tomcat | Apache | 6.0.0 (including) | 6.0.0 (including) |
| Tomcat | Apache | 6.0.1 (including) | 6.0.1 (including) |
| Tomcat | Apache | 6.0.2 (including) | 6.0.2 (including) |
| Tomcat | Apache | 6.0.3 (including) | 6.0.3 (including) |
| Tomcat | Apache | 6.0.4 (including) | 6.0.4 (including) |
| Tomcat | Apache | 6.0.5 (including) | 6.0.5 (including) |
| Tomcat | Apache | 6.0.6 (including) | 6.0.6 (including) |
| Tomcat | Apache | 6.0.7 (including) | 6.0.7 (including) |
| Tomcat | Apache | 6.0.8 (including) | 6.0.8 (including) |
| Tomcat | Apache | 6.0.9 (including) | 6.0.9 (including) |
| Tomcat | Apache | 6.0.10 (including) | 6.0.10 (including) |
| Tomcat | Apache | 6.0.11 (including) | 6.0.11 (including) |
| Tomcat | Apache | 6.0.12 (including) | 6.0.12 (including) |
| Tomcat | Apache | 6.0.13 (including) | 6.0.13 (including) |
| Tomcat | Apache | 6.0.14 (including) | 6.0.14 (including) |
| Tomcat | Apache | 6.0.15 (including) | 6.0.15 (including) |
| Tomcat | Apache | 6.0.16 (including) | 6.0.16 (including) |
| Tomcat | Apache | 6.0.17 (including) | 6.0.17 (including) |
| Tomcat | Apache | 6.0.18 (including) | 6.0.18 (including) |
| Tomcat | Apache | 6.0.19 (including) | 6.0.19 (including) |
| Tomcat | Apache | 6.0.20 (including) | 6.0.20 (including) |
| Tomcat | Apache | 6.0.21 (including) | 6.0.21 (including) |
| Tomcat | Apache | 6.0.22 (including) | 6.0.22 (including) |
| Tomcat | Apache | 6.0.23 (including) | 6.0.23 (including) |
| Tomcat | Apache | 6.0.24 (including) | 6.0.24 (including) |
| Tomcat | Apache | 6.0.25 (including) | 6.0.25 (including) |
| Tomcat | Apache | 6.0.26 (including) | 6.0.26 (including) |
| Tomcat | Apache | 6.0.27 (including) | 6.0.27 (including) |
| Tomcat | Apache | 6.0.28 (including) | 6.0.28 (including) |
| Tomcat | Apache | 6.0.29 (including) | 6.0.29 (including) |
| Tomcat | Apache | 6.0.30 (including) | 6.0.30 (including) |
| Tomcat | Apache | 6.0.31 (including) | 6.0.31 (including) |
| Tomcat | Apache | 6.0.32 (including) | 6.0.32 (including) |
| Tomcat | Apache | 6.0.33 (including) | 6.0.33 (including) |
| Tomcat | Apache | 6.0.34 (including) | 6.0.34 (including) |
| Tomcat | Apache | 6.0.35 (including) | 6.0.35 (including) |
| Tomcat | Apache | 6.0.36 (including) | 6.0.36 (including) |
| Tomcat | Apache | 6.0.37 (including) | 6.0.37 (including) |
| Tomcat | Apache | 6.0.38 (including) | 6.0.38 (including) |
| Tomcat | Apache | 6.0.39 (including) | 6.0.39 (including) |
| Tomcat | Apache | 6.0.40 (including) | 6.0.40 (including) |
| Tomcat | Apache | 6.0.41 (including) | 6.0.41 (including) |
| Tomcat | Apache | 6.0.42 (including) | 6.0.42 (including) |
| Tomcat | Apache | 6.0.43 (including) | 6.0.43 (including) |
| Tomcat | Apache | 6.0.44 (including) | 6.0.44 (including) |
| Tomcat | Apache | 6.0.45 (including) | 6.0.45 (including) |
| Tomcat | Apache | 6.0.46 (including) | 6.0.46 (including) |
| Tomcat | Apache | 6.0.47 (including) | 6.0.47 (including) |
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: