CVE-2019-11288: tcServer JMX Socket Listener Registry Rebinding Local Privilege Escalation
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-11288?
The severity of CVE-2019-11288 is high with a severity value of 7.
What is affected by CVE-2019-11288?
Pivotal tc Server versions prior to 3.2.19 and 4.x versions prior to 4.0.10, and Pivotal tc Runtimes 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 are affected by CVE-2019-11288.
How can a local attacker exploit CVE-2019-11288?
A local attacker can exploit CVE-2019-11288 by exploiting the JMX Socket Listener configuration in a tc Runtime instance.
What is the fix for CVE-2019-11288?
To fix CVE-2019-11288, upgrade to Pivotal tc Server 3.2.19 or later, or Pivotal tc Runtimes 7.0.99.B or later, 8.5.47.A or later, or 9.0.27.A or later.
Where can I find more information about CVE-2019-11288?
You can find more information about CVE-2019-11288 [here](https://pivotal.io/security/cve-2019-11288).