# CVE-2018-2973: Other in Java

> An unauthenticated attacker can modify critical data in Java SE via SSL/TLS, primarily affecting client-side sandboxed applications.

- **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:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** CLEANSTART-2026-JU52681, GHSA-pj6g-h9ch-r92c, MINI-3hcv-3c2q-4273, MINI-h27g-fff2-ch9g, MINI-qhf3-5c5c-7vw2

## What is CVE-2018-2973?

CVE-2018-2973 is a medium-severity vulnerability in Hp Xp7 Command View, 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, Java SE Embedded component of Oracle Java SE (subcomponent: JSSE). Supported versions that are affected are Java SE: 6u191, 7u181, 8u172 and 10.0.1; Java SE Embedded: 8u171. Difficult to exploit vulnerability allows unauthenticated attacker with network access via SSL/TLS 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, 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 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-2018-2973?

It affects 20 products.


Products: Hp Xp7 Command View, Netapp Active Iq Unified Manager, Netapp Cloud Backup, Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Storage Manager, Netapp Oncommand Insight, Netapp Oncommand Unified Manager, Netapp Oncommand Workflow Automation, Netapp Plug-in for Symantec Netbackup, Netapp Snapmanager, Netapp Steelstore Cloud Integrated Storage, Netapp Storage Replication Adapter for Clustered Data Ontap, Netapp Vasa Provider for Clustered Data Ontap, Netapp Virtual Storage Console, Oracle Jdk, Oracle Jre, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, Redhat Satellite.

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

Upgrade to a fixed version.

## Is CVE-2018-2973 being exploited?

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

## Other vulnerabilities in Hp Xp7 Command View

- [CVE-2016-4378](https://insights.sbomify.com/CVE-2016-4378/): Information disclosure in n/a (high 7.5)
- [CVE-2018-2657](https://insights.sbomify.com/CVE-2018-2657/): Denial of service in Java (medium 5.3)
- [CVE-2016-4381](https://insights.sbomify.com/CVE-2016-4381/): Auth bypass in n/a (medium 4.5)
- [CVE-2018-2940](https://insights.sbomify.com/CVE-2018-2940/): Information disclosure in Java (medium 4.3)
- [CVE-2019-2426](https://insights.sbomify.com/CVE-2019-2426/): Information disclosure in Java (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2973 is a medium-severity vulnerability in Hp Xp7 Command View, 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-2973 in the wild and no public exploit code.

Affected product: Hp Xp7 Command View. 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-2973/ (Markdown: https://insights.sbomify.com/CVE-2018-2973/index.md)
```

## Sources

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

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