CVE-2017-16610
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 execute arbitrary code on vulnerable installations of Netgain Enterprise Manager. Authentication is not required to exploit this vulnerability. The specific flaw exists within upload_save_do.jsp. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code under the context of the current user. Was ZDI-CAN-4751.
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 Netgain Enterprise Manager's upload_save_do.jsp allows unauthenticated remote attackers to execute arbitrary code by supplying a malicious path that gets used in file operations without proper validation.
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.766CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Netgain Enterprise Manager is installedCheck for Netgain Enterprise Manager in installed applications or running services on the systemAffected if Netgain Enterprise Manager is present on the system
-
Identify installed versionCheck the application version through its web interface, installer details, or version file within the installation directoryAffected if The installed version is lower than 7.2.766
-
Locate upload_save_do.jspSearch for the upload_save_do.jsp file within the web application's directory structure, typically found in the web root or a servlet/JSP directoryAffected if The file upload_save_do.jsp exists and is accessible via the web application
-
Verify web interface accessibilityAttempt to access the upload_save_do.jsp endpoint via HTTP/HTTPS (e.g., http://[host]/upload_save_do.jsp) from a network location that could reach the applicationAffected if The web interface is externally accessible and the JSP endpoint responds without authentication
-
Check for unauthenticated access controlsReview the application's security configuration and web.xml to determine if authentication is required for the upload_save_do.jsp endpointAffected if No authentication is required to access the upload functionality
The environment is affected if Netgain Enterprise Manager version is below 7.2.766 and the upload_save_do.jsp endpoint is accessible without authentication.
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.
dbcve · scoped7.2.766
Implement strict validation and sanitization of user-supplied file paths, restrict upload locations to non-executable directories, and apply vendor security patches if available.
Netgain Enterprise Manager 7.2.766 or later
- 1. Identify the current version of Netgain Enterprise Manager installed in the environment
- 2. Obtain Netgain Enterprise Manager version 7.2.766 or later from the official vendor
- 3. Create a complete backup of the current system including database and configuration files
- 4. Test the upgrade in a non-production/staging environment first
- 5. Apply the upgrade to production systems during a planned maintenance window
- 6. Verify the upgrade was successful and the service is functioning properly
- 7. Confirm the upload_save_do.jsp file has been updated and the path traversal vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16610 — 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-16610 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