dbcve.org
E Series Santricity Os ControllerApplication · Netapp

CVE-2022-23237

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to after 11.70.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 through 11.70.2 are vulnerable to host header injection attacks that could allow an attacker to redirect users to malicious websites.

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 vulnerability is a host header injection flaw in E-Series SANtricity OS Controller Software versions 11.x through 11.70.2. Attackers can manipulate the HTTP Host header to trick the application into generating malicious redirects to external websites, potentially leading to phishing attacks against users.

MitigationImplement server-side validation of the Host header against an allowlist of permitted values, and configure the web server or application to use a fixed value for URL generation rather than trusting client-supplied input.

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.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify the installed product
    Access the SANtricity System Manager or use the CLI command 'show storage-array' to confirm the system is NetApp E-Series SANtricity OS Controller
    Affected if The product is not E-Series SANtricity OS Controller, this CVE does not apply
  2. Check the SANtricity OS version
    In SANtricity System Manager, go to Support > Support Resources > Software and Firmware Inventory, or use the CLI command 'download driveFirmware' to view the controller OS version
    Affected if The installed version is between 11.0.0 and 11.70.2 inclusive, the system is potentially affected
  3. Verify the web management interface is enabled
    Confirm that the SANtricity web server is running and the management interface is accessible via HTTP/HTTPS on the controller ports (typically 8080/8443)
    Affected if The web interface is disabled or not accessible, the host header injection attack surface may be reduced but the vulnerable code may still exist in the installation

The environment is affected if it runs E-Series SANtricity OS Controller versions 11.0.0 through 11.70.2 with the web management interface enabled, allowing HTTP requests where a manipulated Host header could influence redirect destinations.

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

Implement server-side validation of the Host header against an allowlist of permitted values, and configure the web server or application to use a fixed value for URL generation rather than trusting client-supplied input.

Recommended fix Moderate confidence

SANtricity OS Controller version 11.71.0 or later (the next release after 11.70.2)

  1. 1. Identify the current installed version of E-Series SANtricity OS Controller Software by accessing the SANtricity System Manager or using the command-line interface.
  2. 2. Confirm the installed version falls within the affected range: 11.0.0 through 11.70.2.
  3. 3. Obtain the latest SANtricity OS Controller Software from the NetApp Support site (support.netapp.com) or the NetApp Products Security Advisory.
  4. 4. Review the release notes for the fixed version to understand any changes or requirements.
  5. 5. Follow the NetApp upgrade procedure for SANtricity OS Controller Software, which typically involves: downloading the new OS bundle, uploading it to the storage array through SANtricity System Manager or CLI, and applying the update.
  6. 6. After upgrade, verify the new version is installed and confirm the vulnerability is resolved.
Caveat Refer to SANtricity OS 11.71.0 release notes for any configuration or compatibility changes; minor version upgrades typically have low risk but always review breaking changes documentation

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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