# CVE-2019-2684: Other in Java

> An unauthenticated attacker can modify or delete critical data in Java SE via RMI, requiring patching of the Java runtime environment.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2019
- **Updated:** 2 Oct 2024
- **Also known as:** CLEANSTART-2026-SY32555, DEBIAN-CVE-2019-2684, GHSA-x59f-cpgf-vmmv, MINI-79vf-r295-v2pj, MINI-9rq3-35mp-xmhm, MINI-pwfr-5q2h-45vh, UBUNTU-CVE-2019-2684

## What is CVE-2019-2684?

CVE-2019-2684 is a medium-severity vulnerability in Apache Tomcat, published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: RMI). Supported versions that are affected are Java SE: 7u211, 8u202, 11.0.2 and 12; Java SE Embedded: 8u201. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE, Java SE Embedded accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.0 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).

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

It affects 17 products.


Products: Apache Cassandra, Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Hp Xp7 Command View, Opensuse Leap, Oracle Jdk, Oracle Jre, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Openshift Container Platform, Redhat Satellite.

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

Apply the vendor's patch.

## Is CVE-2019-2684 being exploited?

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

## Other vulnerabilities in Apache Tomcat

- [CVE-2016-3427](https://insights.sbomify.com/CVE-2016-3427/): Oracle Java SE and JRockit Unspecified (critical 9.8, exploited in the wild)
- [CVE-2018-8016](https://insights.sbomify.com/CVE-2018-8016/): Missing Authentication for Critical Function in Apache Cassandra (critical 9.8)
- [CVE-2021-44521](https://insights.sbomify.com/CVE-2021-44521/): Remote code execution for scripted UDFs (critical 9.1)
- [CVE-2026-27314](https://insights.sbomify.com/CVE-2026-27314/): Apache Cassandra: Privilege escalation via ADD IDENTITY authorization bypass (high 8.8)
- [CVE-2025-26467](https://insights.sbomify.com/CVE-2025-26467/): Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions (4.0.16 only) (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2684 is a medium-severity vulnerability in Apache Tomcat, published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-2684 in the wild and no public exploit code.

Affected product: Apache Tomcat. 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-2684/ (Markdown: https://insights.sbomify.com/CVE-2019-2684/index.md)
```

## Sources

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

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