dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-17406

CRITICAL · 9.8 CVSS v3.0 Published 2018-01-23
Fix available
A fix is available. Upgrade to 7.2.766 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
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Netgain Enterprise Manager. Authentication is not required to exploit this vulnerability. The specific flaw exists within an exposed RMI registry, which listens on TCP ports 1800 and 1850 by default. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute arbitrary code under the context of the current process. Was ZDI-CAN-4753.

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

A critical unauthenticated deserialization vulnerability in Netgain Enterprise Manager's exposed RMI registry (TCP ports 1800/1850). The RMI registry lacks proper validation of incoming data, allowing attackers to send malicious serialized Java objects that deserialize into arbitrary code execution under the context of the running process.

MitigationImmediately restrict network access to ports 1800 and 1850 from untrusted sources using firewall rules or network segmentation. If the RMI service is not required, disable it entirely. Apply vendor patches if available.

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
Enterprise ManagerApplication
Affected:< 7.2.766

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 if Netgain Enterprise Manager is installed
    Check common installation paths: on Windows look in C:\Program Files\Netgain or C:\Netgain, on Linux check /opt/netgain or /usr/share/netgain. Also check for running processes named 'Netgain' or 'Enterprise Manager' using task manager or 'ps aux | grep -i netgain'
    Affected if Netgain Enterprise Manager software is found on the system
  2. Determine the installed version
    Check the version of Netgain Enterprise Manager. On Windows, right-click the application in Program Files > Properties > Details. On Linux, check the application JAR or configuration files. Alternatively, look for a 'version' file in the installation directory or check the about/help section of the web interface
    Affected if The version is lower than 7.2.766 (for example, 7.2.500, 7.2.0, etc.)
  3. Check if ports 1800 or 1850 are listening
    Run 'netstat -an | findstr "1800 1850"' on Windows or 'netstat -tuln | grep -E "1800|1850"' on Linux. Also use 'nmap -p 1800,1850 localhost' or 'ss -tuln' to confirm if the RMI registry ports are open and listening
    Affected if Ports 1800 or 1850 are shown as LISTENING or open
  4. Verify network accessibility of RMI ports
    From an external host, test connectivity with 'telnet <target> 1800' or 'nmap -p 1800,1850 <target IP>'. Check firewall rules with 'netsh advfirewall firewall show rule name=all' on Windows or 'iptables -L' on Linux to see if these ports are allowed from untrusted networks
    Affected if Ports 1800/1850 are accessible from untrusted network segments or the internet
  5. Confirm RMI service is in use
    Check Netgain configuration files (typically in the 'config' or 'conf' folder of the installation) for RMI-related settings. Look for java.rmi.registry.port or similar RMI configuration. Use 'jmap -heap <pid>' if you can identify the Java process to inspect JVM settings
    Affected if RMI registry configuration is present and the service is running

You are affected if Netgain Enterprise Manager is installed with a version below 7.2.766 AND ports 1800/1850 are exposed and accessible on your network.

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 7.2.766 or later
Fixed in 7.2.766
Interim mitigation

Immediately restrict network access to ports 1800 and 1850 from untrusted sources using firewall rules or network segmentation. If the RMI service is not required, disable it entirely. Apply vendor patches if available.

Recommended fix Moderate confidence

Netgain Enterprise Manager 7.2.766 or later

  1. 1. Obtain the fixed version of Netgain Enterprise Manager (version 7.2.766 or later) from the official vendor
  2. 2. Before upgrading, backup all existing data and configurations
  3. 3. Stop the Netgain Enterprise Manager service
  4. 4. Install version 7.2.766 or later following the vendor's standard upgrade procedure
  5. 5. Restart the service and verify the RMI registry ports (1800 and 1850) are properly configured
  6. 6. Validate that the application functions correctly after the upgrade

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

Fix this in Enterprise Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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