dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-16595

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 org.apache.jsp.u.jsp.reports.export_005fdownload_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-5118.

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 path traversal vulnerability in NetGain Enterprise Manager's export_download.jsp servlet (port 8081) allows authenticated attackers to read arbitrary files via the filename parameter without proper path validation. Although authentication is required, it can be bypassed, enabling unauthorized file access that may expose sensitive system information.

MitigationImplement strict input validation on the filename parameter to prevent directory traversal (e.g., block '../' sequences, whitelist allowed paths), and ensure authentication bypass is remediated to properly enforce access controls.

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. Verify NetGain Enterprise Manager is running
    Check if port 8081 is open and responding: run 'netstat -an | grep 8081' or 'curl -I http://localhost:8081'
    Affected if Port 8081 is open and the NetGain web interface is accessible
  2. Confirm installed version is 7.2.730
    Locate the NetGain installation directory and check version files, or access the application's about/login page to display the version number
    Affected if The installed version is exactly 7.2.730
  3. Identify presence of vulnerable servlet
    Check for the existence of export_download.jsp in the web application's servlet path, typically in the 'webapps' directory under the NetGain installation
    Affected if The file export_download.jsp exists in the deployed web application
  4. Check authentication enforcement
    Attempt to access the export_download.jsp endpoint without credentials, or review authentication configuration files in the NetGain deployment
    Affected if The servlet can be accessed without valid authentication or authentication can be bypassed
  5. Review filename parameter handling
    Examine the web server logs or proxy logs for requests to export_download.jsp containing '../' sequences in the filename parameter
    Affected if Directory traversal sequences are accepted and processed by the servlet without rejection

If NetGain Enterprise Manager version 7.2.730 is running on port 8081 with the export_download.jsp servlet accessible (especially with bypassed authentication), the environment is likely affected by this path traversal vulnerability.

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

Implement strict input validation on the filename parameter to prevent directory traversal (e.g., block '../' sequences, whitelist allowed paths), and ensure authentication bypass is remediated to properly enforce access controls.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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