CVE-2019-12418: High severity IBM Data Risk Manager vulnerability

Published 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.

Other sources

Apache Tomcat could allow a local attacker to gain elevated privileges on the system, caused by a flaw when configured with the JMX Remote Lifecycle Listener. By using man-in-the-middle attack techniques, an attacker could exploit this vulnerability to capture user names and passwords used to access the JMX interface and gain elevated privileges.

IBM

When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.

When Tomcat is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.

Reference: https://tomcat.apache.org/security-7.html https://tomcat.apache.org/security-8.html http://tomcat.apache.org/security-9.html

Upstream commits: https://github.com/apache/tomcat/commit/bef3f40 https://github.com/apache/tomcat/commit/a91d7db https://github.com/apache/tomcat/commit/1fc9f58

Red Hat

Affected Software

29 affected componentsFixes available
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
IBM Data Risk Manager<=2.0.6
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
redhat/tomcat<7.0.98
7.0.98
redhat/tomcat<8.5.48
8.5.48
redhat/tomcat<9.0.29
9.0.29
debian/tomcat9
9.0.43-2~deb11u109.0.107-0+deb11u29.0.70-29.0.95-19.0.115-1

Remediation

Information

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

Event History

Nov 21, 2019
CVE Published
12:00 AM
Dec 20, 2019
Data Sourced
via Red Hat·05:57 PM
DescriptionSeverityAffected Software
Dec 23, 2019
CVE Published
via MITRE·05:12 PM
Data Sourced
via MITRE·05:12 PM
DescriptionWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityAffected Software
Feb 20, 2026
Data Sourced
via Ubuntu·10:40 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·10:41 PM
Description
Data Sourced
via Debian·10:41 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID of this Apache Tomcat vulnerability?

The vulnerability ID is CVE-2019-12418.

2

What is the severity of CVE-2019-12418?

The severity of CVE-2019-12418 is high, with a severity value of 8.4.

3

How does CVE-2019-12418 impact Apache Tomcat?

CVE-2019-12418 allows a local attacker to manipulate the RMI registry and perform a man-in-the-middle attack to capture usernames.

4

Which versions of Apache Tomcat are affected by CVE-2019-12418?

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.

5

How can I fix CVE-2019-12418 in Apache Tomcat?

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203