E Series Santricity Os ControllerApplication · Netapp

CVE-2021-26996

HIGH · 7.5 CVSS v3.1 Published 2021-06-11
Fix available
A fix is available. Upgrade to 11.70.1 or later.
See remediation →
84/100
Remediation priority · High
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
E-Series SANtricity OS Controller Software 11.x versions prior to 11.70.1 are susceptible to a vulnerability which when successfully exploited could allow a remote attacker to discover system configuration and application information which may aid in crafting more complex attacks.

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

E-Series SANtricity OS Controller Software versions 11.x prior to 11.70.1 contains an information disclosure vulnerability allowing remote unauthenticated attackers to discover system configuration and application details. This reconnaissance capability could expose sensitive infrastructure details useful for planning further attacks.

MitigationUpgrade SANtricity OS Controller Software to version 11.70.1 or later to remediate the vulnerability.

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.0, < 11.70.1

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
None
Availability
None

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

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. Locate the installed SANtricity OS version
    Access the SANtricity System Manager or use the command-line interface (CLI) to retrieve the current OS Controller Software version. This is typically found in the system information or About section of the management interface.
    Affected if The displayed version falls within the range 11.0.0 to 11.70.1 (excluding 11.70.1).
  2. Compare version against the affected range
    Take the installed version number you retrieved and verify whether it is greater than or equal to 11.0.0 AND less than 11.70.1. Any version meeting both conditions is considered affected.
    Affected if The version meets both conditions: version >= 11.0.0 AND version < 11.70.1.
  3. Assess network exposure of the management interface
    Determine whether the SANtricity management interface (typically ports 8443 or 8080 for web-based access) is exposed to untrusted networks or the internet. Review firewall rules, VLAN configurations, and access control lists.
    Affected if The management interface is accessible from untrusted networks without proper access restrictions.
  4. Review access logs for unauthorized reconnaissance
    Examine SANtricity access logs and system logs for evidence of unauthenticated requests that may have queried system configuration, application details, or infrastructure information. Look for repeated queries from external IP addresses.
    Affected if Unauthenticated external requests attempting to enumerate system configuration details are present in the logs.

You are affected if your SANtricity OS Controller Software version is 11.0.0 or higher but lower than 11.70.1, and the management interface is accessible to unauthenticated remote attackers.

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.

From vendor data
Upgrade available Upgrade to 11.70.1 or later
Fixed in 11.70.1
Interim mitigation

Upgrade SANtricity OS Controller Software to version 11.70.1 or later to remediate the vulnerability.

Fix this in E Series Santricity Os Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2021-26996 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