dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-16605

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 overwrite 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.db.save_005fattrs_jsp servlet, which listens on TCP port 8081 by default. When parsing the id 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 overwrite any files accessible to the Administrator. Was ZDI-CAN-5196.

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 confidence

Path traversal vulnerability in NetGain Enterprise Manager's db.save_attrs_jsp servlet (TCP port 8081). The id parameter is not validated before file operations, allowing authenticated attackers to overwrite arbitrary files on the system via directory traversal sequences.

MitigationRestrict network access to port 8081, implement strict input validation on the id parameter to prevent directory traversal, and apply vendor security patches when 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.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
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NetGain Enterprise Manager installation
    Check if NetGain Enterprise Manager is installed by searching for its installation directory, process, or service. Common paths may include C:\Program Files\NetGain or /opt/netgain. Look for running processes named 'NetGain' or 'Enterprise Manager'.
    Affected if NetGain Enterprise Manager is installed and running on the system
  2. Verify port 8081 is accessible
    Check if TCP port 8081 is listening and exposed. Use 'netstat -an | findstr 8081' on Windows or 'netstat -tuln | grep 8081' on Linux. Verify if the port is bound to a listening service.
    Affected if Port 8081 is open and listening, indicating the web interface is accessible
  3. Determine installed version
    Check the version of NetGain Enterprise Manager. Look for version information in the installation directory, service properties, or check the application's about/help page. Compare against version 7.2.730.
    Affected if The installed version matches 7.2.730 exactly, or falls within any known affected version range
  4. Confirm db.save_attrs_jsp endpoint exists
    Access or probe the endpoint /db.save_attrs_jsp on the server at port 8081 (e.g., http://target:8081/db.save_attrs_jsp). Check if the servlet is present and responds to requests.
    Affected if The db.save_attrs_jsp servlet is accessible and responds to requests
  5. Review authentication configuration
    Examine the web application's authentication settings for the management interface on port 8081. Check if default credentials are in use or if authentication can be bypassed.
    Affected if The application uses weak, default, or no authentication for the vulnerable servlet

The system is affected if NetGain Enterprise Manager version 7.2.730 is running with port 8081 exposed and the db.save_attrs_jsp servlet is accessible without proper input validation on the id parameter.

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 network access to port 8081, implement strict input validation on the id parameter to prevent directory traversal, and apply vendor security patches when available.

Fix this in Enterprise Manager 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 help mitigating

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-2017-16605 — 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-16605 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