dbcve.org
Santricity Storage ManagerApplication · Netapp

CVE-2018-5488

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-13
Fix available
A fix is available. Upgrade to after 11.42.0x00.0001 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The NetApp SANtricity Web Services Proxy and Storage Manager ship with the Java Management Extension Remote Method Invocation (JMX RMI) service exposed on the network without authentication. This allows remote attackers to inject and execute arbitrary Java code on the affected system by leveraging the unprotected JMX RMI interface, resulting in complete system compromise.

MitigationDisable or restrict the JMX RMI service, apply network segmentation to prevent external access, or upgrade to a patched version of SANtricity Web Services Proxy and SANtricity Storage Manager beyond the affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Santricity Storage ManagerApplication
Affected:>= 11.30.0x00.0004, <= 11.42.0x00.0001
Santricity Web Services ProxyApplication
Affected:>= 1.10.x000.0002, <= 2.12.x000.0002

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SANtricity product and version
    Locate the SANtricity Storage Manager or Web Services Proxy installation directory and check the version information file or executable properties. Common locations include /opt/netapp/santricity or Program Files\NetApp\SANtricity on Windows. Use 'smversion' command or check version files in the installation directory.
    Affected if The installed version falls within 11.30.0x00.0004 to 11.42.0x00.0001 for Storage Manager, or 1.10.x000.0002 to 2.12.x000.0002 for Web Services Proxy.
  2. Verify JMX RMI service is running
    Check for running Java processes related to SANtricity. On Linux/Unix, use 'ps aux | grep -i santricity' or 'ps aux | grep java'. On Windows, check services or running processes for JMX-related entries. Look for JMX RMI registry processes typically listening on ports 1099 or 30000-39999 range.
    Affected if JMX RMI service process is actively running as part of SANtricity.
  3. Check network binding configuration
    Determine which network interfaces the JMX RMI service is bound to. Use 'netstat -anp' or 'ss -anp' on Linux to see if the JMX RMI port is listening on 0.0.0.0 (all interfaces) rather than 127.0.0.1 (localhost only). On Windows, use 'netstat -ano' or check service configuration.
    Affected if The JMX RMI port is listening on 0.0.0.0 or an external network interface, making it accessible from other hosts.
  4. Confirm remote accessibility
    From a different host on the network, attempt to connect to the JMX RMI port using a tool like 'nc -zv <target> <port>' or 'telnet <target> <port>' to verify the port is exposed externally, not just locally accessible.
    Affected if The JMX RMI port responds to connection attempts from remote systems, indicating network exposure.

You are affected if SANtricity Storage Manager or Web Services Proxy is installed within the vulnerable version range AND the JMX RMI service is running and accessible from network addresses other than localhost.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 11.42.0x00.0001
Interim mitigation

Disable or restrict the JMX RMI service, apply network segmentation to prevent external access, or upgrade to a patched version of SANtricity Web Services Proxy and SANtricity Storage Manager beyond the affected versions.

Recommended fix Moderate confidence

SANtricity Storage Manager >= 11.42.0x00.0002 or SANtricity Web Services Proxy >= 2.12.x000.0003

  1. 1. Identify the currently installed SANtricity Storage Manager or SANtricity Web Services Proxy version
  2. 2. Download the latest patched version from the NetApp support portal at https://mysupport.netapp.com
  3. 3. For SANtricity Storage Manager, upgrade to version 11.42.0x00.0002 or later
  4. 4. For SANtricity Web Services Proxy, upgrade to version 2.12.x000.0003 or later
  5. 5. Verify the upgrade completed successfully by checking the product version
  6. 6. Confirm the JMX RMI service is no longer exposed to unauthenticated network access
Caveat Review NetApp release notes for the target version to check for any configuration or feature changes that may affect existing setups

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Santricity Storage Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-5488 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-5488 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data