CVE-2015-0779
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 · uneditedDirectory traversal vulnerability in UploadServlet in Novell ZENworks Configuration Management (ZCM) 10 and 11 before 11.3.2 allows remote attackers to execute arbitrary code via a crafted directory name in the uid parameter, in conjunction with a WAR filename in the filename parameter and WAR content in the POST data, a different vulnerability than CVE-2010-5323 and CVE-2010-5324.
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 confidenceDirectory traversal vulnerability in Novell ZENworks Configuration Management's UploadServlet allows remote attackers to upload arbitrary WAR (Web Application Archive) files to the filesystem by manipulating the uid parameter to contain path traversal sequences (e.g., ../../../), combined with specifying a malicious WAR filename and content. This enables remote code execution by deploying and invoking the uploaded web shell.
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= 11= 11.2= 11.2.1= 11.2.2= 11.2.3CVSS 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
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 ZCM installation and versionLocate the ZCM installation directory and check the version file or use the ZCM command line tools (zxpnsh -v or similar) to retrieve the installed version number.Affected if The installed version matches exactly 11, 11.2, 11.2.1, 11.2.2, or 11.2.3.
-
Verify UploadServlet endpoint accessibilityIdentify the web server port (typically 8080 for HTTP or 8443 for HTTPS) and attempt to access the UploadServlet endpoint using a standard path such as /zenworks/UploadServlet or /servlet/UploadServlet. Check if the endpoint responds to POST requests.Affected if The UploadServlet is reachable without authentication or with low-privilege credentials.
-
Examine HTTP access logs for path traversal attemptsReview the web server access logs (located in the ZCM logs directory or web container logs) for requests to the UploadServlet containing uid parameter values with ../ sequences or other path traversal patterns.Affected if Logs show requests to UploadServlet with uid parameters containing ../ or similar path traversal sequences.
-
Check for unexpected WAR file deploymentsSearch the filesystem for WAR files deployed in non-standard directories outside the normal application deployment folder, particularly in the root directory or configuration folders.Affected if WAR files exist in unexpected locations that could indicate successful exploitation.
A system is affected if it runs ZCM version 11, 11.2, 11.2.1, 11.2.2, or 11.2.3 with the UploadServlet accessible over the network.
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 · scopedUpgrade to ZCM 11.3.2 or later to patch the directory traversal vulnerability in UploadServlet. If immediate patching is not feasible, restrict network access to the UploadServlet endpoint and monitor for suspicious path traversal patterns in uid parameters.
ZENworks Configuration Management 11.3.2
- Download Zenworks Configuration Management 11.3.2 from the official Novell/SUSE vendor site
- Review the ZCM 11.3.2 release notes for any pre-upgrade requirements
- Ensure proper backups of the ZCM database and configuration are completed
- Stop all ZCM services before beginning the upgrade
- Install ZCM 11.3.2 following the standard upgrade procedure
- Verify all ZCM services start successfully after upgrade
- Confirm the UploadServlet vulnerability is no longer present by verifying the patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0779 — 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-2015-0779 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