Skip to content

Insufficiently Protected Credentials in Apache Tomcat

High severity GitHub Reviewed Published Dec 26, 2019 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.tomcat.embed:tomcat-embed-core (Maven)

Affected versions

< 7.0.98
>= 8.0.0, < 8.5.48
>= 9.0.0, < 9.0.29

Patched versions

7.0.99
8.5.49
9.0.29

Description

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.

References

Published by the National Vulnerability Database Dec 23, 2019
Reviewed Dec 26, 2019
Published to the GitHub Advisory Database Dec 26, 2019
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.047%
(19th percentile)

Weaknesses

CVE ID

CVE-2019-12418

GHSA ID

GHSA-hh3j-x4mc-g48r

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.