# CVE-2019-2602: Denial of service in Java

> Unauthenticated attackers can cause a complete denial of service in Java SE by sending malicious data to specific library APIs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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-DB02708, DEBIAN-CVE-2019-2602, GHSA-cq96-vcc6-mj28, MINI-jmw2-6jgf-mqm5, MINI-q6g7-6w66-7rq3, MINI-wjpx-62h3-fqrj, UBUNTU-CVE-2019-2602

## What is CVE-2019-2602?

CVE-2019-2602 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, 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: Libraries). Supported versions that are affected are Java SE: 7u211, 8u202, 11.0.2 and 12; Java SE Embedded: 8u201. Easily exploitable 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 ability to cause a hang or frequently repeatable crash (complete DOS) of Java SE, Java SE Embedded. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.0 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 16 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Hp Xp7 Command View, Mcafee Epolicy Orchestrator, 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-2602?

Apply the vendor's patch.

## Is CVE-2019-2602 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2602 is a high-severity denial of service vulnerability in Canonical Ubuntu Linux, 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-2602 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-2602/ (Markdown: https://insights.sbomify.com/CVE-2019-2602/index.md)
```

## Sources

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

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