CVE-2017-16604
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 · uneditedThis 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.cnnic.asset.deviceReport.deviceReport_005fexport_005fdo_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 vulnerability to overwrite any files accessible to the Administrator. Was ZDI-CAN-5195.
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 confidenceA path traversal vulnerability in the deviceReport_export_do.jsp servlet of NetGain Enterprise Manager allows remote attackers to overwrite arbitrary files by manipulating the filename parameter. While authentication is required, the auth mechanism can be bypassed, enabling unauthenticated file writes to any location accessible to the Administrator account.
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= 7.2.730CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetGain Enterprise Manager installationCheck if NetGain Enterprise Manager is installed on the system by looking for its installation directory, service processes, or running applications on common ports such as 8081Affected if NetGain Enterprise Manager is installed and running on the system
-
Verify the installed versionLocate and read the version information for NetGain Enterprise Manager, typically found in the application itself, an about page, or version files within the installation directoryAffected if The installed version is exactly 7.2.730
-
Confirm the vulnerable servlet existsCheck if the deviceReport_export_do.jsp file exists in the web application directory, typically under the webapps or ROOT directory of the NetGain installationAffected if The deviceReport_export_do.jsp servlet is present in the web application path
-
Check network exposure of port 8081Determine if the NetGain web interface on port 8081 is exposed to network access, as this is where the vulnerable servlet residesAffected if Port 8081 is accessible from untrusted networks or the internet
-
Test servlet accessibilityAttempt to access the deviceReport_export_do.jsp endpoint via HTTP request to verify it is reachable, such as http://target:8081/deviceReport_export_do.jspAffected if The servlet responds to HTTP requests and is not otherwise restricted
A system is affected if NetGain Enterprise Manager version 7.2.730 is installed with the deviceReport_export_do.jsp servlet accessible on port 8081, allowing potential path traversal exploitation despite authentication requirements.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict access to the affected servlet on port 8081, implement strict path validation to prevent directory traversal sequences (../), and apply any available vendor patches for this vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-16604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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