CVE-2017-5201
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 · uneditedNetApp Clustered Data ONTAP before 8.3.2P8 and 9.0 before P2 allow remote authenticated users to obtain sensitive cluster and tenant information via unspecified vectors, a different vulnerability than CVE-2016-3064.
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 · moderate confidenceNetApp Clustered Data ONTAP versions before 8.3.2P8 and 9.0 before P2 contain an information disclosure vulnerability allowing remote authenticated users to obtain sensitive cluster and tenant information through unspecified vectors.
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< 8.3.2= 9.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NetApp Clustered Data ONTAP is installedIdentify the installed storage operating system product name in your environmentAffected if Product is NetApp Clustered Data ONTAP (other NetApp products are not affected by this CVE)
-
Retrieve the exact installed version numberUse the system command or interface to display the current Clustered Data ONTAP version (for example, ontap-version or system node show -fields version)Affected if Unable to determine exact version (vulnerability status cannot be verified)
-
Check if version is in the 8.x line before 8.3.2P8Compare your installed 8.x version against 8.3.2P8 - note that any version before 8.3.2P8 is affectedAffected if Installed version is 8.3.2 or earlier (for example, 8.3.2, 8.3.1, 8.3.0, etc.) and patch level is below P8
-
Check if version is in the 9.0 line before P2Compare your installed 9.0 version against 9.0P2 - note that version 9.0 before patch 2 is affectedAffected if Installed version is 9.0 without P2 applied (9.0, 9.0P1, or earlier)
-
Verify if remote authentication is enabledCheck whether remote authentication (such as LDAP, Active Directory, or other remote authentication methods) is configured for cluster accessAffected if Remote authentication is enabled - this is required for the unauthenticated attacker vector mentioned in the CVE
Your environment is affected if NetApp Clustered Data ONTAP is installed with version 8.3.2 before P8, or version 9.0 before P2, and remote authentication is enabled for cluster or tenant access.
Generated from the published advisory. Verify against your own configuration.
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 data8.3.2
Upgrade NetApp Clustered Data ONTAP to version 8.3.2P8, 9.0 P2, or later to patch this information disclosure vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5201 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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