dbcve.org
Oncommand Workflow AutomationApplication · Netapp

CVE-2015-3292

HIGH · 10.0 CVSS v2.0 Published 2015-05-31
Fix available
A fix is available. Upgrade to after 2.2.1 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 installer in NetApp OnCommand Workflow Automation before 2.2.1P1 and 3.x before 3.0P1 sets up the Java Debugging Wire Protocol (JDWP) service, which allows remote attackers to execute arbitrary code 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 confidence

The NetApp OnCommand Workflow Automation installer enables the Java Debugging Wire Protocol (JDWP) service, which listens on a network port without authentication. JDWP is a debugging protocol that allows full interaction with the JVM including class loading, thread inspection, and method invocation. When exposed remotely, attackers can inject and execute arbitrary Java code on the target system with the privileges of the running process.

MitigationApply the vendor patches (upgrade to version 2.2.1P1 or 3.0P1 and later) which remove the JDWP service from the installer. If patching is not immediately possible, verify the JDWP port is not listening or is firewalled from untrusted networks.

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 Workflow AutomationApplication
Affected:<= 2.2.1= 3.0

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 Workflow Automation installation
    Locate the OnCommand Workflow Automation installation directory, typically under /opt/netapp/ocw or C:\Program Files\NetApp\ocw on Windows. Check for the presence of the ocw or OnCommand Workflow Automation software suite.
    Affected if OnCommand Workflow Automation is installed on the system
  2. Determine installed version
    Check the installed version by examining version files in the installation directory, typically found in a version.info, VERSION, or similar file within the installation folder. Compare against affected versions <=2.2.1 or exactly 3.0.
    Affected if Installed version is 2.2.1 or earlier, or exactly 3.0
  3. Check for JDWP network listener
    Use netstat or ss to scan for listening ports commonly associated with JDWP (default port 5005, but may vary). Run: netstat -anp | grep LISTEN (Linux) or netstat -an | findstr LISTEN (Windows) and look for Java processes bound to network ports.
    Affected if A Java process is listening on a network port accessible from non-localhost interfaces without authentication
  4. Verify JDWP process is running
    Check running processes for Java debugging components. Use ps aux | grep -i jdwp or check Windows services for Java debugging-related services that were installed by the OnCommand Workflow Automation installer.
    Affected if JDWP debugging service process is running and exposed on the network

The system is affected if NetApp OnCommand Workflow Automation version 2.2.1 or earlier (or exactly version 3.0) is installed AND a JDWP service is listening on a network port accessible from remote systems.

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 2.2.1
Interim mitigation

Apply the vendor patches (upgrade to version 2.2.1P1 or 3.0P1 and later) which remove the JDWP service from the installer. If patching is not immediately possible, verify the JDWP port is not listening or is firewalled from untrusted networks.

Recommended fix High confidence

Upgrade to OnCommand Workflow Automation 2.2.1P1 (for 2.x installations) or 3.0P1 (for 3.x installations)

  1. 1. Back up the current OnCommand Workflow Automation installation and configuration
  2. 2. Download the patched version from the NetApp support portal: either version 2.2.1P1 (for the 2.x branch) or version 3.0P1 (for the 3.x branch)
  3. 3. Stop the OnCommand Workflow Automation service
  4. 4. Install the patched version following the standard upgrade procedure documented in the NetApp installation guide
  5. 5. Verify the JDWP service is not exposed by confirming no debug port (typically port 5005) is listening on external interfaces
  6. 6. Restart the OnCommand Workflow Automation service
  7. 7. Validate the application is functioning correctly and confirm the fix is applied
Caveat Review NetApp release notes for 2.2.1P1 and 3.0P1 for any compatibility notes or known issues before upgrading

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

Fix this in Oncommand Workflow Automation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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