dbcve.org
Ontap System ManagerApplication · Netapp

CVE-2021-27004

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-01
Fix available
A fix is available. Upgrade to 9.7 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

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
System Manager 9.x versions 9.7 and higher prior to 9.7P16, 9.8P7 and 9.9.1P2 are susceptible to a vulnerability which could allow a local attacker to discover plaintext iSCSI CHAP credentials.

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

A detailed technical summary for this CVE is being prepared.

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
Ontap System ManagerApplication
Affected:>= 9.0, < 9.7= 9.7= 9.8= 9.9.12

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 9.7 or later
Fixed in 9.7
Vendor patch security.netapp.com →
Recommended fix High confidence

ONTAP 9.7 to 9.7P16, or 9.8 to 9.8P7, or 9.9.x to 9.9.1P2 (or later stable releases)

  1. 1. Identify the current ONTAP System Manager version by logging into System Manager and viewing the version information, or by running 'system node image' command in ONTAP CLI.
  2. 2. Based on the current version, plan the upgrade path to the appropriate fixed patch release: For ONTAP 9.7.x, upgrade to 9.7P16 or later. For ONTAP 9.8.x, upgrade to 9.8P7 or later. For ONTAP 9.9.x, upgrade to 9.9.1P2 or later.
  3. 3. Download the appropriate patched release from the NetApp Support Site under the 'Downloads' section for ONTAP.
  4. 4. Review NetApp's upgrade pre-check requirements and ensure prerequisites are met before initiating the upgrade.
  5. 5. Perform the upgrade using System Manager or ONTAP CLI, following NetApp's standard upgrade procedures.
  6. 6. After upgrade completion, verify the new version is running by checking System Manager or running 'system node image' in CLI.
Caveat Ensure compatibility with existing configurations and review NetApp upgrade guidelines for any temporary service interruptions during the upgrade process

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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