CVE-2014-0600
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 · uneditedFileUploadServlet in the Administration service in Novell GroupWise 2014 before SP1 allows remote attackers to read or write to arbitrary files via the poLibMaintenanceFileSave parameter, aka ZDI-CAN-2287.
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 confidenceFileUploadServlet in the Administration service of Novell GroupWise 2014 before SP1 contains a path traversal vulnerability via the poLibMaintenanceFileSave parameter, allowing remote attackers to read or write arbitrary files on the server. This is a classic unrestricted file write vulnerability in the admin interface.
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= 2014CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GroupWise installation and versionLocate the GroupWise installation directory and check the version information, typically found in the installation path or via the GroupWise administration tools. Look for version 2014 and determine if SP1 is applied.Affected if GroupWise 2014 is installed and the version is 2014 without Service Pack 1 applied (e.g., 2014.0.x before SP1).
-
Verify Administration service is runningCheck if the GroupWise Administration service is active, typically listening on port 9710. Use netstat or similar network tools to confirm the service is bound and accepting connections.Affected if The Administration service is running and accessible on the network.
-
Confirm admin interface accessibilityAttempt to access the Administration web interface by navigating to the server on port 9710 (e.g., https://server:9710 or http://server:9710) to verify the servlet is available.Affected if The FileUploadServlet is accessible without authentication or with compromised admin credentials.
-
Check network exposure of admin portReview firewall rules and network configuration to determine if port 9710 is exposed to untrusted networks or the public internet.Affected if Port 9710 is accessible from untrusted networks or the internet, allowing remote attackers to reach the vulnerable servlet.
A user is affected if GroupWise 2014 without SP1 is installed and the Administration service (port 9710) is accessible, enabling remote path traversal exploitation via the FileUploadServlet.
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 dataUpgrade to GroupWise 2014 SP1 or later to obtain the patched servlet. If immediate patching is not feasible, restrict network access to the Administration service port (typically port 9710) using firewall rules or network segmentation to prevent unauthorized external access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0600 — 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-2014-0600 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