`CVE-2019-11288`

Affected software	2 products, listed below
Severity	7.0 High CVSS 3.1 3 scores
Weakness	Improper privilege management (CWE-269)
Published	27 Jan 2020
Updated	17 Jun 2026

Description

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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 6 years ago.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC none indexed
EPSS 0.27% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

VRT has not found a public code change for this CVE yet.

Protection none
Action not pursued
Review automated Upstream data
Record active

Decided by	Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read
Finding	This CVE affects a known product, but nothing published names a fix and nothing published shows an exploit. That is a statement about the evidence, not about the defect — it does not mean the vulnerability is unimportant or unreachable, only that neither of the two things VRT can act on exists.

Decided by

Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

Finding

This CVE affects a known product, but nothing published names a fix and nothing published shows an exploit. That is a statement about the evidence, not about the defect — it does not mean the vulnerability is unimportant or unreachable, only that neither of the two things VRT can act on exists.

CVSS

7.0 HIGH v3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H 3 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 7.0 HIGH CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H NVD Primary published

CVSS 3.0 7.3 HIGH CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H security@pivotal.io Secondary

CVSS 2.0 1.9 none AV:L/AC:M/Au:N/C:P/I:N/A:N NVD Primary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	7.0	HIGH	`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`	NVD	Primary	published
CVSS 3.0	7.3	HIGH	`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`	security@pivotal.io	Secondary
CVSS 2.0	1.9	none	`AV:L/AC:M/Au:N/C:P/I:N/A:N`	NVD	Primary

Affected software and releases

Products and versions

2 products, 5 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	pivotal	tc runtimes	generic	≥ 7.0.70 and ＜ 7.0.99 · ≥ 8.5.4 and ＜ 8.5.47 · ≥ 9.0.6 and ＜ 9.0.27
nvd	pivotal	tc server	generic	≥ 3.0.0 and ＜ 3.2.19 · ≥ 4.0.0 and ＜ 4.0.10

Source

Vendor

Product

Scheme

Affected versions

nvd

pivotal

tc runtimes

generic

≥ 7.0.70 and ＜ 7.0.99 · ≥ 8.5.4 and ＜ 8.5.47 · ≥ 9.0.6 and ＜ 9.0.27

nvd

pivotal

tc server

generic

≥ 3.0.0 and ＜ 3.2.19 · ≥ 4.0.0 and ＜ 4.0.10

References

URL	Tags
https://pivotal.io/security/cve-2019-11288	Vendor Advisory

URL

Timeline

Published	2020-01-27	By the CVE Program.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.

Published

2020-01-27

By the CVE Program.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

How VRT decided (19 of 24 rules ran)

19 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven no match An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package no match An affected Maven artifact named by the CNA itself

11 known-cpe-product matched In scope Matches known products: pivotal/tc_server

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint no match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven no match The affected package being open source on Maven, so the fix can be read

19 poc-derivable no match An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit decided it matched No exploit published No public exploits or POCs found in Exploit-DB, Nuclei templates, Metasploit modules, or GitHub POC repositories, and CISA's Vulnrichment assessment records no demonstrated exploit. No upstream fix reference or open-source Maven package was found either, so there is nothing to act on from either direction.

21 secure-rule-match no match A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold skipped Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published skipped Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

pivotal tc_runtimes not tracked cpe:2.3:a:pivotal:tc_runtimes:*:*:*:*:*:*:*:*

pivotal tc_server tracked cpe:2.3:a:pivotal:tc_server:*:*:*:*:*:*:*:* yaml

NVD ↗ · CVE.org ↗