dbcve.org
Enterprise ManagerApplication · Netgain Systems

CVE-2017-16608

CRITICAL · 9.8 CVSS v3.0 Published 2018-01-23
Fix available
A fix is available. Upgrade to 7.2.766 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 arbitrary code on vulnerable installations of Netgain Enterprise Manager. Authentication is not required to exploit this vulnerability. The specific flaw exists within exec.jsp. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code under the context of the current user. Was ZDI-CAN-4749.

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

This is an unauthenticated remote code execution vulnerability in Netgain Enterprise Manager's exec.jsp file. The flaw stems from insufficient validation of user-supplied input before it's passed to a system call, allowing attackers to execute arbitrary commands on the underlying operating system.

MitigationApply vendor-provided patch immediately. If no patch is available, restrict access to exec.jsp via network-level controls or web application firewall rules until a fix can be deployed.

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

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

CVSS:3.0/AV:N/AC:L/PR:N/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. Identify Netgain Enterprise Manager installation
    Locate the Netgain installation directory. Common paths include C:\Program Files\Netgain or /opt/netgain. Check for the presence of the Netgain Enterprise Manager application files, particularly the 'webapps' or 'ROOT' directory containing JSP files.
    Affected if Netgain Enterprise Manager is installed on the system.
  2. Determine the installed version
    Check for a version file or manifest within the Netgain installation directory. Common locations include a version.properties file, README, or the application's WEB-INF/classes folder. The version number is typically displayed in the application's login page footer or in the admin interface.
    Affected if The installed version is lower than 7.2.766.
  3. Locate and verify exec.jsp presence
    Navigate to the web application's JSP directory. The exec.jsp file is typically found in the web root or admin directory, such as /webapps/ROOT/exec.jsp or /webapps/netgain/exec.jsp. Search the entire webapps directory for files named 'exec.jsp'.
    Affected if The exec.jsp file exists in the web application's accessible directory structure.
  4. Check exec.jsp accessibility
    Attempt to access the exec.jsp file via HTTP/HTTPS request to the server, for example: http://<server>:port/exec.jsp or http://<server>:port/netgain/exec.jsp. Verify if the page loads and accepts parameters.
    Affected if The exec.jsp file is accessible via web request without authentication.

The environment is affected if Netgain Enterprise Manager is installed with a version lower than 7.2.766 and the exec.jsp file is accessible on the web server.

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.

dbcve · scoped
Upgrade available Upgrade to 7.2.766 or later
Fixed in 7.2.766
Interim mitigation

Apply vendor-provided patch immediately. If no patch is available, restrict access to exec.jsp via network-level controls or web application firewall rules until a fix can be deployed.

Recommended fix High confidence

Netgain Enterprise Manager 7.2.766 or later stable release

  1. Obtain Netgain Enterprise Manager version 7.2.766 or later from the official vendor
  2. Follow Netgain's standard upgrade procedure to install the updated version
  3. After upgrade, verify that exec.jsp no longer allows unsanitized command execution
  4. Confirm the application is running the patched version through the admin interface or system information

Generated from the published advisory — verify against the referenced sources before acting.

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 the upgrade done

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