dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-16599

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 delete 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.reports.templates.misc.sample_jsp servlet, which listens on TCP port 8081 by default. When parsing the type 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-5190.

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 sample_jsp servlet allows remote attackers to delete arbitrary files via the type parameter without proper path validation. Although authentication is required, the authentication mechanism can be bypassed, enabling unauthenticated file deletion attacks that can be chained with other vulnerabilities for code execution.

MitigationImplement strict input validation on the type parameter to restrict file operations to allowed directories, fix the authentication bypass mechanism, and apply vendor-provided 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.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 if NetGain Enterprise Manager is installed
    Check for the application in common installation directories (e.g., C:\Program Files\NetGain Systems\Enterprise Manager or /opt/netgain/enterprise-manager) and look for the service process running on common ports (8080, 8443, or 8090).
    Affected if The application is installed and running.
  2. Verify the installed version matches the affected release
    Locate the version file or check the application's About/Status page. Common paths include: the version.properties file in the installation directory, or accessing the application's main status endpoint which displays the version number.
    Affected if The version is exactly 7.2.730.
  3. Confirm the sample_jsp servlet is present and accessible
    Attempt to access the sample_jsp endpoint via HTTP request to paths such as: /sample_jsp?type=../../conf/filename or /jsp/sample_jsp?type=../../conf/filename. The servlet typically exists under the /jsp/ context path.
    Affected if The sample_jsp servlet responds to requests (returns HTTP 200 or error messages indicating the parameter is processed).
  4. Test for the authentication bypass
    Send a direct request to the sample_jsp endpoint without providing authentication credentials. The vulnerability allows bypassing the login mechanism by making direct servlet requests. Check if the endpoint responds without redirecting to a login page.
    Affected if The servlet processes requests without requiring authentication (no redirect to login, no 401/403 error).

If NetGain Enterprise Manager version 7.2.730 is running with the sample_jsp servlet accessible (especially without proper authentication), the environment is affected by CVE-2017-16599.

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 type parameter to restrict file operations to allowed directories, fix the authentication bypass mechanism, and apply vendor-provided patches if available.

Fix this in Enterprise Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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