dbcve.org
Zenworks Configuration ManagementApplication · Novell

CVE-2010-5323

HIGH · 10.0 CVSS v2.0 Published 2015-06-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Directory traversal vulnerability in UploadServlet in the Remote Management component in Novell ZENworks Configuration Management (ZCM) 10 before 10.3 allows remote attackers to execute arbitrary code via a crafted WAR pathname in the filename parameter in conjunction with WAR content in the POST data, a different vulnerability than 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 confidence

Directory traversal vulnerability in the UploadServlet of Novell ZENworks Configuration Management (ZCM) 10 Remote Management component allows remote attackers to upload arbitrary files by manipulating the WAR pathname in the filename parameter combined with malicious WAR content in the POST data, enabling remote code execution.

MitigationUpgrade to ZCM 10.3 or later which contains the patch for this vulnerability. If immediate patching is not possible, consider disabling or restricting access to the Remote Management component until the upgrade can be applied.

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
Zenworks Configuration ManagementApplication
Affected:= 10.0= 10.1= 10.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ZCM version
    Check the installed version of Novell ZENworks Configuration Management. This can typically be found in the product's about page, installation logs, or by querying theZENworks server services. On Windows, check the 'Add/Remove Programs' entry or theZENworks installation directory for version information.
    Affected if The installed version is 10.0, 10.1, or 10.2.
  2. Confirm Remote Management component is enabled
    Access the ZENworks Administration Console and navigate to the Remote Management settings. Verify whether the Remote Management feature is currently enabled. This component is typically configured under Configuration > Remote Management or similar administration pages.
    Affected if Remote Management is enabled and the version is 10.0, 10.1, or 10.2.
  3. Check for UploadServlet exposure
    Inspect network-accessible endpoints for the ZENworks Remote Management servlet. The vulnerable endpoint is typically accessible at a path containing 'UploadServlet' or similar upload-related servlets under the Remote Management web application. Review web server configuration and deployed WAR files in the application server hosting the Remote Management component.
    Affected if The UploadServlet endpoint is accessible over the network and the version is 10.0, 10.1, or 10.2.

A user is affected if they are running ZENworks Configuration Management version 10.0, 10.1, or 10.2 with the Remote Management component enabled and the UploadServlet endpoint is network-accessible.

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
Patch available Apply the vendor patch
Vendor patch www.novell.com →
Interim mitigation

Upgrade to ZCM 10.3 or later which contains the patch for this vulnerability. If immediate patching is not possible, consider disabling or restricting access to the Remote Management component until the upgrade can be applied.

Recommended fix High confidence

ZENworks Configuration Management 10.3

  1. Obtain ZENworks Configuration Management 10.3 from Novell's official download channels or support site
  2. Review the official Novell support KB article 7005573 for specific upgrade instructions
  3. Create a complete backup of the current ZCM configuration and database
  4. Stop all ZCM services before beginning the upgrade process
  5. Install or upgrade to ZCM version 10.3 following the documented upgrade procedure
  6. Restart ZCM services after the upgrade completes
  7. Verify the Remote Management component is functioning correctly and the UploadServlet vulnerability is resolved
Caveat Review Novell ZCM 10.3 release notes for any configuration or feature changes from prior 10.x versions

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

Fix this in Zenworks Configuration Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the patch applied

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-5323 — 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-2010-5323 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