CVE-2017-8919
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 OnCommand API Services before 1.2P3 logs the LDAP BIND password when a user attempts to log in using the REST API, which allows remote authenticated users to obtain sensitive password 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 · high confidenceNetApp OnCommand API Services versions prior to 1.2P3 contain a logging mechanism that inadvertently captures LDAP BIND passwords in plaintext when users attempt authentication through the REST API. This creates an information disclosure vulnerability where any remote authenticated attacker with log file access can recover valid LDAP credentials.
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<= 1.2CVSS 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.1/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 installed OnCommand API Services versionRun the following command to check the version: ocapi --version or check the /opt/netapp/lib/ocum/version file if accessible via shell. Alternatively, access the API services web UI and look at the version displayed in the About or System Information section.Affected if The installed version is 1.2 or any version prior to 1.2P3.
-
Determine if LDAP authentication is configuredCheck the OnCommand API Services configuration for LDAP settings. This can typically be done through the administration UI under Authentication or LDAP settings, or by inspecting the configuration files in /opt/netapp/ocapi/config/ directory for LDAP bind credentials or user directory settings.Affected if LDAP authentication is enabled and configured with an LDAP bind DN and password.
-
Examine log files for plaintext LDAP passwordsAccess the log files for OnCommand API Services, typically located in /opt/netapp/ocapi/logs/ or /var/log/ocapi/. Search through the log files (such as api.log, audit.log, or auth.log) for strings matching the configured LDAP bind password or patterns that appear to be passwords in plaintext.Affected if Log files contain any plaintext LDAP bind passwords or credentials that match the LDAP configuration.
-
Check for historical log files and backupsReview any archived or rotated log files in the logs directory, as well as any backup copies of log files. Also check for log files that may have been exported or copied to other locations.Affected if Archived or backup log files contain plaintext LDAP credentials.
A user is affected if they are running OnCommand API Services version 1.2 or earlier with LDAP authentication enabled and their log files contain plaintext LDAP bind passwords.
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 NetApp OnCommand API Services to version 1.2P3 or later. Additionally, rotate any LDAP credentials that may have been exposed in logs prior to the upgrade.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8919 — 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-8919 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