# CVE-2018-5488: Code injection in SANtricity Products

> Unauthenticated remote code execution is possible in NetApp SANtricity products due to the JMX RMI service being exposed on the network.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** No
- **Published:** 13 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vwv4-7jrf-phmx

## What is CVE-2018-5488?

CVE-2018-5488 is a critical code injection vulnerability in NetApp SANtricity Products, published on 13 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NetApp SANtricity Web Services Proxy versions 1.10.x000.0002 through 2.12.X000.0002 and SANtricity Storage Manager 11.30.0X00.0004 through 11.42.0X00.0001 ship with the Java Management Extension Remote Method Invocation (JMX RMI) service bound to the network, and are susceptible to unauthenticated remote code execution.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Netapp Santricity Storage Manager, Netapp Santricity Web Services Proxy.

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

No fix has been published for CVE-2018-5488 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-5488 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5488 is a critical code injection vulnerability in NetApp SANtricity Products, published on 13 Jun 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-5488 in the wild and no public exploit code.

Affected product: NetApp SANtricity Products. 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-5488/ (Markdown: https://insights.sbomify.com/CVE-2018-5488/index.md)
```

## Sources

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

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