CVE-2017-7947
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.2P11, 9.0 before P4, and 9.1 before P5 allow attackers to obtain sensitive password information by leveraging logging of passwords entered non-interactively on the command line.
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 confidenceNetApp Clustered Data ONTAP contains a vulnerability where passwords entered non-interactively on the command line are inadvertently written to system logs. An attacker with access to these logs can obtain sensitive password information, potentially leading to unauthorized access to the storage system or connected resources.
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.0= 9.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/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.
-
Identify Clustered Data ONTAP versionRun the command 'version' or 'system node show' from the clustered Data ONTAP command-line interface (CLI) to retrieve the installed versionAffected if The version displayed is 8.3.2, 9.0, or 9.1 exactly (these are the specific affected versions)
-
Check system logs for command-line passwordsAccess log files in /etc/log/messages or /var/log/messages (depending on Data ONTAP operating mode) and search for patterns matching password entries or CLI commands that may contain credentialsAffected if Plaintext passwords or password strings appear in system logs
-
Review audit logs for credential exposureUse the 'security login show' or 'event log show' commands in Data ONTAP CLI to examine audit trails for any commands that contained password argumentsAffected if Audit logs contain commands with password parameters visible in plain text
-
Examine shell history filesCheck /root/.bash_history or similar shell history files on the storage controller for any commands that included passwords entered interactivelyAffected if Shell history contains commands with passwords specified as arguments
You are affected if you run Clustered Data ONTAP version 8.3.2, 9.0, or 9.1 AND your system logs, audit logs, or shell history contain plaintext passwords from command-line entries.
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 to Clustered Data ONTAP 8.3.2P11, 9.0P4, 9.1P5 or later. Additionally, review existing log files for exposed credentials and rotate any passwords that may have been logged.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7947 — 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-7947 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