dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-16606

HIGH · 8.8 CVSS v3.0 Published 2018-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 code by creating arbitrary files on vulnerable installations of NetGain Systems Enterprise Manager 7.2.730 build 1034. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the org.apache.jsp.u.jsp._3d.add_005f3d_005fview_005fdo_jsp servlet, which listens on TCP port 8081 by default. When parsing the filename parameter, the process does not properly validate a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code under the context of Administrator. Was ZDI-CAN-5197.

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

NetGain Enterprise Manager contains a path traversal vulnerability in the /u.jsp/_3d/add_3d_view_do.jsp servlet on port 8081. The filename parameter is not validated before file operations, allowing authenticated attackers (via bypass mechanism) to write arbitrary files and execute code as Administrator.

MitigationRestrict file write operations with strict allowlist-based path validation, fix the authentication bypass mechanism, and restrict the servlet to authorized users only.

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.730

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

CVSS:3.0/AV:N/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. Confirm NetGain Enterprise Manager installation
    Check for the application in typical installation directories such as C:\Program Files\NetGain or C:\NetGain, or look for a Windows service named 'NetGain Enterprise Manager' using 'sc query' or 'Get-Service' in PowerShell
    Affected if The software is not found or the service does not exist, then the system is not affected by this specific CVE
  2. Verify installed version is 7.2.730
    Check the version of NetGain Enterprise Manager by examining the JAR files in the installation directory, the Windows service properties, or any version file. Compare against the affected version 7.2.730
    Affected if The installed version equals 7.2.730 exactly, indicating the system matches the affected version
  3. Check if port 8081 is listening
    Run 'netstat -an | findstr :8081' or 'Get-NetTCPConnection -LocalPort 8081' in PowerShell to determine if the application service is actively listening on the vulnerable port
    Affected if Port 8081 is open and listening, meaning the vulnerable servlet is network-accessible
  4. Confirm the vulnerable servlet exists
    Inspect the web application deployment in the NetGain installation directory, specifically look for the path /u.jsp/_3d/add_3d_view_do.jsp or the corresponding class file in the webapps or similar directory structure
    Affected if The vulnerable servlet file exists in the deployment, indicating the attack surface is present
  5. Check for authentication bypass exposure
    Review the application's authentication configuration and determine if the authentication bypass mechanism mentioned in the CVE is present or if the /u.jsp/_3d/ path is accessible without proper authentication
    Affected if The vulnerable endpoint can be accessed without valid authentication, enabling the path traversal attack

A system is affected if it runs NetGain Enterprise Manager version 7.2.730 with port 8081 open and the vulnerable servlet accessible, particularly if the authentication bypass allows unauthenticated access to the add_3d_view_do.jsp endpoint

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict file write operations with strict allowlist-based path validation, fix the authentication bypass mechanism, and restrict the servlet to authorized users only.

Fix this in Enterprise Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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