# CVE-2019-11288: tcServer JMX Socket Listener Registry Rebinding Local Privilege Escalation

> Local attackers can hijack JMX RMI registry to steal credentials and gain full control over the tc Runtime instance.

- **Severity:** High 7.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gfwv-ggwh-qj2r

## What is CVE-2019-11288?

CVE-2019-11288 is a high-severity vulnerability in Pivotal tc Server 3.x, published on 27 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2019-11288?

It affects 2 products.


Products: Pivotal Tc Runtimes, Pivotal Tc Server.

## How do I fix CVE-2019-11288?

No fix has been published for CVE-2019-11288 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-11288 being exploited?

There is no known exploitation of CVE-2019-11288 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11288 and fix it if it is affected.

What it is: CVE-2019-11288 is a high-severity vulnerability in Pivotal tc Server 3.x, published on 27 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-11288 in the wild and no public exploit code.

Affected product: Pivotal tc Server 3.x. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11288/ (Markdown: https://insights.sbomify.com/CVE-2019-11288/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11288
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11288
- OSV: https://osv.dev/vulnerability/CVE-2019-11288

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11288/
Summaries are generated and may contain mistakes; the official description above is the record.