dbcve.org
Oncommand Unified ManagerApplication · Netapp

CVE-2018-5486

HIGH · 7.8 CVSS v3.0 Published 2018-04-25
Fix available
A fix is available. Upgrade to after 7.3 or later.
See remediation →
80/100
Remediation priority · High
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
NetApp OnCommand Unified Manager for Linux versions 7.2 though 7.3 ship with the Java Debug Wire Protocol (JDWP) enabled which allows unauthorized local attackers to execute arbitrary code.

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

NetApp OnCommand Unified Manager for Linux versions 7.2-7.3 ships with Java Debug Wire Protocol (JDWP) enabled, a debugging interface that accepts connections without authentication. This allows any local user to attach a debugger to the Java process and execute arbitrary code with the privileges of the application.

MitigationDisable or remove JDWP in production deployments. NetApp should be consulted for vendor-provided patches or configuration guidance to securely disable the debugging interface.

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 Unified ManagerApplication
Affected:>= 7.2, <= 7.3

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

CVSS:3.0/AV:L/AC:L/PR:L/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 the installed OnCommand Unified Manager version
    Run the following command to query the product version: /opt/netapp/um/bin/ocum -version or check /opt/netapp/um/VERSION file. Alternatively, use the package manager: rpm -qa | grep -i unified-manager or dpkg -l | grep -i unified-manager
    Affected if The version number returned is 7.2, 7.3, or any version within the 7.2 to 7.3 range (inclusive)
  2. Locate the Java process running OnCommand Unified Manager
    Run: ps aux | grep -i java | grep -i um\|ocum or look for Java processes associated with the NetApp Unified Manager installation directory /opt/netapp/um/
    Affected if A Java process related to OnCommand Unified Manager is running
  3. Check for JDWP debug port listening
    Run: netstat -tlnp | grep -E '5005|8000|8080' or ss -tlnp | grep -E '5005|8000|8080' to check for debug or management ports. Also run: lsof -i -P | grep java to identify Java processes with open network connections
    Affected if A Java process is listening on a port typically used for debugging (such as 5005) or any unexpected port that accepts remote debug connections
  4. Inspect Java process startup arguments for JDWP flags
    Run: ps aux | grep java and examine the full command line for flags such as -agentlib:jdwp, -Xrunjdwp, -javaagent, or transport=dt_socket, which indicate JDWP debugging is enabled
    Affected if The Java process command line contains JDWP-related arguments like -agentlib:jdwp, -Xrunjdwp, or transport=dt_socket with suspend=n or on
  5. Verify if debug port accepts unauthenticated connections
    Attempt to connect to the identified debug port using a Java debugger tool or netcat: nc -zv localhost <debug_port> or telnet localhost <debug_port> to confirm the port accepts connections without authentication
    Affected if The debug port is open and accepts connections without requiring authentication credentials

A user is affected if OnCommand Unified Manager version 7.2 or 7.3 is installed and the Java process is running with JDWP debugging enabled and accessible, allowing unauthenticated local users to attach a debugger.

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.

From vendor data
Upgrade available Upgrade to a release after 7.3
Interim mitigation

Disable or remove JDWP in production deployments. NetApp should be consulted for vendor-provided patches or configuration guidance to securely disable the debugging interface.

Fix this in Oncommand Unified Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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