dbcve.org
Clustered Data OntapApplication · Netapp

CVE-2017-12423

HIGH · 7.7 CVSS v3.0 Published 2017-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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 Clustered Data ONTAP 8.3.x before 8.3.2P12 allows remote authenticated users to read data on other Storage Virtual Machines (SVMs) via unspecified vectors.

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

This vulnerability in NetApp Clustered Data ONTAP 8.3.x before 8.3.2P12 allows an authenticated user on one Storage Virtual Machine (SVM) to read data belonging to other SVMs, representing a cross-tenant information disclosure due to insufficient SVM isolation.

MitigationUpgrade to Clustered Data ONTAP 8.3.2P12 or later. Review SVM access controls and data access policies to ensure proper tenant isolation is enforced.

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
Clustered Data OntapApplication
Affected:= 8.3= 8.3.1= 8.3.2= 8.3.2p11

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify the installed Clustered Data ONTAP version
    Run the 'version' command or use 'system node image' to display the current ONTAP software version
    Affected if The version displayed is 8.3, 8.3.1, 8.3.2, or 8.3.2P11 (any version before 8.3.2P12)
  2. Confirm multiple Storage Virtual Machines exist
    Use the 'vserver show' command to list all SVMs configured in the cluster
    Affected if More than one SVM is configured, creating a multi-tenant environment where tenant isolation is relevant
  3. Review SVM access controls and data access policies
    Examine SVM-level access configurations using 'vserver export-policy' and 'vserver cifs share' commands to inspect how data access is restricted between SVMs
    Affected if Policies allow cross-SVM data access or lack proper tenant isolation rules

You are affected if your Clustered Data ONTAP version is between 8.3 and 8.3.2P11 inclusive and you have multiple SVMs configured where insufficient isolation may permit cross-tenant data reads.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Clustered Data ONTAP 8.3.2P12 or later. Review SVM access controls and data access policies to ensure proper tenant isolation is enforced.

Fix this in Clustered Data Ontap Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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