dbcve.org
Oncommand InsightApplication · Netapp

CVE-2017-5600

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-02
Fix available
A fix is available. Upgrade to after 7.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The Data Warehouse component in NetApp OnCommand Insight before 7.2.3 allows remote attackers to obtain administrative access by leveraging a default privileged account.

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

The Data Warehouse component in NetApp OnCommand Insight versions before 7.2.3 contains a default privileged account with hardcoded credentials that allows unauthenticated remote attackers to gain administrative access to the system.

MitigationImmediately change or disable the default privileged account credentials and upgrade to OnCommand Insight version 7.2.3 or later to remediate this vulnerability.

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
Oncommand InsightApplication
Affected:<= 7.2.2

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 OnCommand Insight installation and version
    Locate the OnCommand Insight installation and determine the installed version number. This is typically found in the product's about or system information page, or via command-line tools provided by the product.
    Affected if The installed version is 7.2.2 or earlier (any version <= 7.2.2)
  2. Confirm Data Warehouse component is configured
    Verify that the Data Warehouse component is enabled or configured within the OnCommand Insight installation. Check the component status through the admin console or configuration files.
    Affected if Data Warehouse is enabled and the OnCommand Insight version is <= 7.2.2
  3. Check for default privileged account
    Inspect user accounts configured in the Data Warehouse or system administration section. Look for accounts that may have been set up by default during installation, particularly any privileged or administrative accounts.
    Affected if A default privileged account with hardcoded credentials exists and has not been changed or disabled
  4. Review access logs for unauthorized administrative activity
    Examine Data Warehouse and system access logs for any remote authentication attempts or administrative actions from unfamiliar sources or IP addresses, especially successful logins that occurred without proper credential provisioning.
    Affected if Unauthorized administrative access or unusual remote authentication activity is present in the logs

You are affected if OnCommand Insight version 7.2.2 or earlier is installed with the Data Warehouse component enabled and the default privileged account credentials remain unchanged.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.2.2
Interim mitigation

Immediately change or disable the default privileged account credentials and upgrade to OnCommand Insight version 7.2.3 or later to remediate this vulnerability.

Recommended fix Moderate confidence

7.2.3 or later (latest stable release)

  1. 1. Identify the current OnCommand Insight version by checking the Data Warehouse component
  2. 2. Confirm the version is 7.2.2 or earlier (vulnerable)
  3. 3. Plan maintenance window for upgrade - this may require system downtime
  4. 4. Backup the OnCommand Insight configuration and any critical data
  5. 5. Download OnCommand Insight version 7.2.3 or later from the NetApp support portal
  6. 6. Follow NetApp's official upgrade documentation for your deployment type (standalone or clustered)
  7. 7. Perform the upgrade to version 7.2.3 or latest stable release
  8. 8. After upgrade, verify the Data Warehouse component is running the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Oncommand Insight Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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