# CVE-2018-2938: Code injection in Java

> Unauthenticated attackers can compromise Java SE via network access, leading to full system takeover through code execution.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** CLEANSTART-2026-YR99837, GHSA-3vhh-58w3-43m4, MINI-6x9f-qpw6-p3wg

## What is CVE-2018-2938?

CVE-2018-2938 is a critical code injection vulnerability in Netapp Active Iq Unified Manager, 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: Java DB). Supported versions that are affected are Java SE: 6u191, 7u181 and 8u172. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. While the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. 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. CVE-2018-2938 addresses CVE-2018-1313. CVSS 3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).

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

It affects 15 products.


Products: 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.

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

Apply the vendor's patch.

## Is CVE-2018-2938 being exploited?

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

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2022-31692](https://insights.sbomify.com/CVE-2022-31692/): Spring Security authorization rules can be bypassed via forward or include dispatcher types (critical 9.8)
- [CVE-2022-2526](https://insights.sbomify.com/CVE-2022-2526/): Use after free in systemd-resolved (critical 9.8)
- [CVE-2022-22978](https://insights.sbomify.com/CVE-2022-22978/): Authorization bypass in Spring Security (critical 9.8)
- [CVE-2021-22931](https://insights.sbomify.com/CVE-2021-22931/): Code injection in Node (critical 9.8)
- [CVE-2018-2941](https://insights.sbomify.com/CVE-2018-2941/): Code injection in Java (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2938 is a critical code injection vulnerability in Netapp Active Iq Unified Manager, 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-2938 in the wild and no public exploit code.

Affected product: Netapp Active Iq Unified Manager. 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-2938/ (Markdown: https://insights.sbomify.com/CVE-2018-2938/index.md)
```

## Sources

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

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