# CVE-2019-2745: Information disclosure in Java

> An unauthenticated attacker with local access can exploit a Java SE Security flaw to gain unauthorized access to critical data.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2019
- **Updated:** 1 Oct 2024
- **Also known as:** CLEANSTART-2026-FG52357, CLEANSTART-2026-TM97973, DEBIAN-CVE-2019-2745, GHSA-ff2w-wwj3-c5m5, MINI-5mq7-f7pm-4gx4, MINI-9j8f-fv48-vmc8, MINI-g2j9-4p3w-3gpx, UBUNTU-CVE-2019-2745

## What is CVE-2019-2745?

CVE-2019-2745 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 23 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Security). Supported versions that are affected are Java SE: 7u221, 8u212 and 11.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Java SE executes to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java SE 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.1 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

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

It affects 7 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Hp Xp7 Command View, Mcafee Epolicy Orchestrator, Opensuse Leap, Oracle Jdk, Oracle Jre.

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

Upgrade to a fixed version.

## Is CVE-2019-2745 being exploited?

There is no known exploitation of CVE-2019-2745 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-2745 and fix it if it is affected.

What it is: CVE-2019-2745 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 23 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-2745 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-2745/ (Markdown: https://insights.sbomify.com/CVE-2019-2745/index.md)
```

## Sources

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

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