CVE-2020-8585
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 · uneditedOnCommand Unified Manager Core Package versions prior to 5.2.5 may disclose sensitive account information to unauthorized users via the use of PuTTY Link (plink).
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 confidenceOnCommand Unified Manager Core Package versions prior to 5.2.5 contain a vulnerability where PuTTY Link (plink) may expose sensitive account information to unauthorized users, likely through improper handling of credentials or session data in logging or connection contexts.
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< 5.2.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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.
-
Verify OnCommand Unified Manager is installedCheck for OnCommand Unified Manager installation by looking for the product in your system inventory, or check common installation directories such as /opt/netapp/ocum or C:\Program Files\NetApp\OnCommand Unified ManagerAffected if OnCommand Unified Manager is present on the system
-
Identify the installed versionRun the following command to retrieve the version: oncmd -version (Linux/Unix) or check the Windows Registry under HKLM\Software\NetApp\OnCommand Unified Manager\CurrentVersion, or look for a version file in the installation directoryAffected if The installed version is anything prior to 5.2.5 (e.g., 5.2.4, 5.2.3, 5.1.x, etc.)
-
Determine if plink is configured or in useSearch for plink.exe (Windows) or plink (Linux/Unix) within the OnCommand Unified Manager installation directory and associated configuration files. Check for plink paths in environment variables or connection profilesAffected if plink executable exists within the OnCommand Unified Manager environment or is referenced in its configuration
-
Review logging and connection configurationsExamine OnCommand Unified Manager log directories and connection configuration files (typically in /opt/ocum/data or similar data directories) for entries containing plink commands or stored credentials. Look for log files that may capture connection strings or authentication dataAffected if Logs or configuration files contain plink commands with embedded credentials or sensitive account information visible in plain text
You are affected if OnCommand Unified Manager is installed with a version prior to 5.2.5 AND plink is used within the environment, as the credential exposure only occurs when plink is configured for remote connections.
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 data5.2.5
Upgrade OnCommand Unified Manager Core Package to version 5.2.5 or later. Until patched, restrict access to systems using plink and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8585 — 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-2020-8585 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