tcServer JMX Socket Listener Registry Rebinding Local Privilege Escalation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.10, 3.2.19, 7.0.99.B, 8.5.47.A, 9.0.27.A
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In Pivotal tc Server, 3.x versions prior to 3.2.19 and 4.x versions prior to 4.0.10, and Pivotal tc Runtimes, 7.x versions prior to 7.0.99.B, 8.x versions prior to 8.5.47.A, and 9.x versions prior to 9.0.27.A, when a tc Runtime instance is configured with the JMX Socket Listener, a local attacker without access to the tc Runtime 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 tc Runtime instance.
Timeline
- CVE published
- Record last updated
Affected versions
- Pivotal Pivotal tc Server 4.x
fixed in 4.0.10
- Pivotal Pivotal tc Server 3.x
fixed in 3.2.19
- Pivotal Pivotal tc Server 4.x Runtimes
From 7.x · fixed in 7.0.99.B; From 8.x · fixed in 8.5.47.A; From 9.x · fixed in 9.0.27.A
- Pivotal Pivotal tc Server 3.x Runtimes
From 7.x · fixed in 7.0.99.B; From 8.x · fixed in 8.5.47.A