# CVE-2018-2972: Information disclosure in Java

> An unauthenticated attacker can exploit a Java SE Security vulnerability to gain unauthorized access to critical data via network protocols.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-4236-7hj3-75v7, MINI-ccqc-rxxx-q58g, MINI-vqcg-5pvh-9r5r, UBUNTU-CVE-2018-2972

## What is CVE-2018-2972?

CVE-2018-2972 is a medium-severity vulnerability in Oracle Jdk, published on 18 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Security). The supported version that is affected is Java SE: 10.0.1. 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 access to critical data or complete access to all Java SE accessible data. Note: Applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It can also be exploited by supplying data to APIs in the specified Component without using sandboxed Java Web Start applications or sandboxed Java applets, such as through a web service. CVSS 3.0 Base Score 5.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

## Which versions are affected by CVE-2018-2972?

It affects 2 products.


Products: Oracle Jdk, Oracle Jre.

## How do I fix CVE-2018-2972?

Apply the vendor's patch.

## Is CVE-2018-2972 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2972 and fix it if it is affected.

What it is: CVE-2018-2972 is a medium-severity vulnerability in Oracle Jdk, published on 18 Jul 2018. 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-2018-2972 in the wild and no public exploit code.

Affected product: Oracle Jdk. 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-2018-2972/ (Markdown: https://insights.sbomify.com/CVE-2018-2972/index.md)
```

## Sources

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

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