dbcve.org
E Series Santricity Os ControllerApplication · Netapp

CVE-2018-5492

CRITICAL · 9.8 CVSS v3.0 Published 2018-10-04
Fix available
A fix is available. Upgrade to after 11.40 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 E-Series SANtricity OS Controller Software 11.30 and later version 11.30.5 is 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

NetApp E-Series SANtricity OS Controller Software versions 11.30 through 11.30.5 contains a vulnerability allowing unauthenticated remote code execution, enabling attackers to execute arbitrary commands on affected storage controller systems without any credentials.

MitigationApply the appropriate NetApp patch for SANtricity OS Controller Software; if no patch available, consider network segmentation and restricting management interface access until remediation is possible.

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
E Series Santricity Os ControllerApplication
Affected:>= 11.0, <= 11.40

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 SANtricity OS Controller version
    Access the SANtricity controller management interface (System Manager) or use the command line interface (via telnet/SSH to the controller) and locate the OS firmware version information, typically found under Hardware or System Information sections
    Affected if The installed SANtricity OS version falls within 11.0 through 11.40 (any 11.x version at or above 11.0 and at or below 11.40)
  2. Confirm the system is an E-Series storage system
    Verify that the affected storage array is part of the NetApp E-Series product line (E-Series models include E2700, E5600, E5700, EF-Series, etc.) by checking the system model or product name in the controller management interface
    Affected if The storage system is a NetApp E-Series array running the vulnerable SANtricity OS version
  3. Assess management interface exposure
    Review network configuration to determine if the SANtricity management interface (typically ports 8443 or 8080 for web-based access, or port 22 for CLI) is accessible from untrusted or external network segments
    Affected if The management interface is exposed to networks that are not strictly trusted or are external-facing, which enables the unauthenticated attack vector

The environment is affected if it runs SANtricity OS Controller Software versions 11.0 through 11.40 on NetApp E-Series storage systems with an accessible management interface.

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.40
Interim mitigation

Apply the appropriate NetApp patch for SANtricity OS Controller Software; if no patch available, consider network segmentation and restricting management interface access until remediation is possible.

Recommended fix Moderate confidence

A fixed SANtricity OS release beyond 11.30.5 (verify current fixed version on NetApp support site)

  1. 1. Identify the current SANtricity OS version on the E-Series controller by accessing the SANtricity System Manager or using the controller CLI
  2. 2. Download the latest SANtricity OS version from the NetApp support site (support.netapp.com) after verifying the fixed release
  3. 3. Schedule a maintenance window as the update may require controller downtime
  4. 4. Back up the E-Series storage system configuration
  5. 5. Upload the new SANtricity OS file to the controller via SANtricity System Manager or the CLI
  6. 6. Follow NetApp's documented upgrade procedure for E-Series controllers to apply the update
  7. 7. Verify the controller reports the new version and all volumes are online post-upgrade
Caveat Review NetApp release notes for any firmware/hardware compatibility considerations before upgrading

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

Fix this in E Series Santricity Os Controller Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-5492 — 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-5492 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