dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-16592

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 disclose sensitive information 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 common.download_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 in conjunction with other vulnerabilities to execute code in the context of Administrator. Was ZDI-CAN-5103.

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

Path traversal vulnerability in NetGain Enterprise Manager's common.download_jsp servlet on TCP port 8081. The filename parameter is not properly validated before use in file operations, allowing authenticated attackers to read arbitrary files from the filesystem. Although authentication is required, the authentication mechanism can be bypassed, enabling remote file disclosure.

MitigationRestrict network access to port 8081, implement strict input validation on the filename parameter to prevent path traversal, and apply any available vendor patches to address both the path traversal and authentication bypass issues.

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if NetGain Enterprise Manager is installed
    Check for running processes or installed files related to NetGain Enterprise Manager. Look for the application in standard installation directories or check running services on the system.
    Affected if NetGain Enterprise Manager software is present on the system
  2. Verify the installed version
    Access the web interface or check application files to determine the exact version number. Compare against the affected version 7.2.730.
    Affected if The installed version is exactly 7.2.730
  3. Confirm TCP port 8081 is accessible
    Check if port 8081 is listening and accessible on the affected system using network scanning tools or by examining listening ports (e.g., netstat, nmap).
    Affected if Port 8081 is open and accepting connections
  4. Test the vulnerable servlet endpoint
    Attempt to access the common.download_jsp endpoint with a crafted filename parameter containing path traversal sequences (e.g., ../../) to verify if the servlet processes such requests.
    Affected if The servlet responds to requests on port 8081 and processes the filename parameter without proper validation

A system is affected if NetGain Enterprise Manager version 7.2.730 is installed with TCP port 8081 accessible and the common.download_jsp servlet responds to path traversal sequences in the filename 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 filename parameter to prevent path traversal, and apply any available vendor patches to address both the path traversal and authentication bypass issues.

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-16592 — 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-16592 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