First published: Thu Nov 21 2019(Updated: )
A privilege escalation flaw was found in Tomcat when the JMX Remote Lifecycle Listener was enabled. A local attacker without access to the Tomcat process or configuration files could be able to manipulate the RMI registry to perform a man-in-the-middle attack. The attacker could then capture user names and passwords used to access the JMX interface and gain complete control over the Tomcat instance.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/tomcat7 | <0:7.0.70-38.ep7.el6 | 0:7.0.70-38.ep7.el6 |
redhat/tomcat8 | <0:8.0.36-42.ep7.el6 | 0:8.0.36-42.ep7.el6 |
redhat/tomcat-native | <0:1.2.23-21.redhat_21.ep7.el6 | 0:1.2.23-21.redhat_21.ep7.el6 |
redhat/tomcat7 | <0:7.0.70-38.ep7.el7 | 0:7.0.70-38.ep7.el7 |
redhat/tomcat8 | <0:8.0.36-42.ep7.el7 | 0:8.0.36-42.ep7.el7 |
redhat/tomcat-native | <0:1.2.23-21.redhat_21.ep7.el7 | 0:1.2.23-21.redhat_21.ep7.el7 |
redhat/jws5-tomcat | <0:9.0.30-3.redhat_4.1.el6 | 0:9.0.30-3.redhat_4.1.el6 |
redhat/jws5-tomcat-native | <0:1.2.23-4.redhat_4.el6 | 0:1.2.23-4.redhat_4.el6 |
redhat/jws5-tomcat | <0:9.0.30-3.redhat_4.1.el7 | 0:9.0.30-3.redhat_4.1.el7 |
redhat/jws5-tomcat-native | <0:1.2.23-4.redhat_4.el7 | 0:1.2.23-4.redhat_4.el7 |
redhat/jws5-tomcat | <0:9.0.30-3.redhat_4.1.el8 | 0:9.0.30-3.redhat_4.1.el8 |
redhat/jws5-tomcat-native | <0:1.2.23-4.redhat_4.el8 | 0:1.2.23-4.redhat_4.el8 |
redhat/tomcat | <7.0.98 | 7.0.98 |
redhat/tomcat | <8.5.48 | 8.5.48 |
redhat/tomcat | <9.0.29 | 9.0.29 |
Apache Tomcat | >=7.0.0<=7.0.97 | |
Apache Tomcat | >=8.5.0<=8.5.47 | |
Apache Tomcat | >=9.0.0<=9.0.28 | |
Debian Debian Linux | =8.0 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 | |
Oracle Workload Manager | =12.2.0.1 | |
Oracle Workload Manager | =18c | |
Oracle Workload Manager | =19c | |
Canonical Ubuntu Linux | =16.04 | |
openSUSE Leap | =15.1 | |
NetApp OnCommand System Manager | >=3.0.0<=3.1.3 | |
IBM Data Risk Manager | <=2.0.6 | |
debian/tomcat9 | 9.0.43-2~deb11u10 9.0.70-2 |
Disable JMX Remote if monitoring is only needed locally and there is no need to monitor Tomcat remotely. If JMX Remote is required and cannot be disabled, then use the built-in remote JMX facilities provided by the JVM. Please note that JMX Remote Lifecycle Listener is now deprecated and may be removed from both Tomcat 7 [1] and Tomcat 9 [2] after 2020-12-31. [1] https://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html#Deprecated_Implementations [2] https://tomcat.apache.org/tomcat-9.0-doc/config/listeners.html#Deprecated_Implementations
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
The vulnerability ID is CVE-2019-12418.
The severity of CVE-2019-12418 is high, with a severity value of 8.4.
CVE-2019-12418 allows a local attacker to manipulate the RMI registry and perform a man-in-the-middle attack to capture usernames.
Apache Tomcat versions 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, and 7.0.0 to 7.0.97 are affected by CVE-2019-12418.
To fix CVE-2019-12418, update to Apache Tomcat version 7.0.98, 8.5.48, or 9.0.29, depending on the applicable version.