Skip to content
Fencer Intel
high 7.3

CVE-2019-11288 json

tcServer JMX Socket Listener Registry Rebinding Local Privilege Escalation

published 6y ago modified 4mo ago also EUVD-2019-2974

cvss
7.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

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.

Patch / fix

  • Pivotal Pivotal tc Server 4.x 4.0.10
  • Pivotal Pivotal tc Server 3.x 3.2.19
  • Pivotal Pivotal tc Server 4.x Runtimes 7.0.99.B, 8.5.47.A, 9.0.27.A
  • Pivotal Pivotal tc Server 3.x Runtimes 7.0.99.B, 8.5.47.A

Is CVE-2019-11288 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 7.3 CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • Pivotal Pivotal tc Server 4.x
  • Pivotal Pivotal tc Server 3.x
  • Pivotal Pivotal tc Server 4.x Runtimes
  • Pivotal Pivotal tc Server 3.x Runtimes

Classification

Weakness
  • CWE-269 Improper Privilege Management

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.