CVE-2017-5995
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 · uneditedThe NetApp ONTAP Select Deploy administration utility 2.0 through 2.2.1 might allow remote attackers to obtain sensitive information 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 · moderate confidenceNetApp ONTAP Select Deploy administration utility versions 2.0 through 2.2.1 contains an information disclosure vulnerability that could allow remote unauthenticated attackers to obtain sensitive information. The CVSS 3.0 score of 7.5 indicates network-level exploitation with partial confidentiality impact and no authentication required. The specific vectors and nature of exposed data are not detailed in available documentation.
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= 2.0= 2.1= 2.2= 2.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ONTAP Select Deploy installationLocate the NetApp ONTAP Select Deploy administration utility in your environment. This is typically deployed as a Linux VM or appliance. Check your inventory or deployed systems for the presence of the Deploy utility.Affected if The ONTAP Select Deploy administration utility is present in the environment
-
Determine the installed versionAccess the Deploy utility system and check its version. This can typically be done via the utility's web interface, CLI, or by checking system files. Compare the displayed version number against the affected versions.Affected if The installed version is 2.0, 2.1, 2.2, or 2.2.1
-
Confirm the vulnerability conditionVerify that the Deploy utility version falls within the affected range of 2.0 through 2.2.1 inclusive. Any version in this range is affected by the information disclosure vulnerability.Affected if The version matches 2.0, 2.1, 2.2, or 2.2.1
The environment is affected if the ONTAP Select Deploy administration utility version is 2.0, 2.1, 2.2, or 2.2.1, as these versions contain the information disclosure vulnerability allowing remote unauthenticated 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 dataUpgrade ONTAP Select Deploy to version 2.2.2 or later per NetApp's advisory. Review access logs for any unauthorized access attempts to the administration utility during the vulnerable period.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2017-5995 — 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-5995 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