# CVE-2019-2977: Information disclosure in Java

> Unauthenticated attackers can read sensitive data and cause partial denial of service in Java SE via network access.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2019
- **Updated:** 1 Oct 2024
- **Also known as:** CLEANSTART-2026-BT70378, DEBIAN-CVE-2019-2977, GHSA-37wc-j2j9-6vmf, MINI-6x79-fp2p-c9h8, MINI-jmxr-8f45-469x, MINI-m78j-32wm-m5r7, MINI-q3q7-f9p7-mg9q, UBUNTU-CVE-2019-2977

## What is CVE-2019-2977?

CVE-2019-2977 is a medium-severity vulnerability in Debian Debian Linux, published on 16 Oct 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 product of Oracle Java SE (component: Hotspot). Supported versions that are affected are Java SE: 11.0.4 and 13. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Java SE accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Java SE. 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 does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.0 Base Score 4.8 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L).

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

It affects 10 products.


Products: Debian Debian Linux, Netapp Active Iq Unified Manager, Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Storage Manager, Netapp E-Series Santricity Unified Manager, Netapp E-Series Santricity Web Services Proxy, Netapp Oncommand Workflow Automation, Netapp Snapmanager, Oracle Jdk, Oracle Jre.

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

Upgrade to a fixed version.

## Is CVE-2019-2977 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2977 is a medium-severity vulnerability in Debian Debian Linux, published on 16 Oct 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-2977 in the wild and no public exploit code.

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

## Sources

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

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