dbcve.org
Zenworks Configuration ManagementApplication · Novell

CVE-2013-1080

HIGH · 10.0 CVSS v2.0 Published 2013-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click

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
The web server in Novell ZENworks Configuration Management (ZCM) 10.3 and 11.2 before 11.2.4 does not properly perform authentication for zenworks/jsp/index.jsp, which allows remote attackers to conduct directory traversal attacks, and consequently upload and execute arbitrary programs, via a request to TCP port 443.

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

Novell ZENworks Configuration Management contains an authentication bypass vulnerability in the web server component for the zenworks/jsp/index.jsp file. Remote attackers can exploit improper authentication combined with directory traversal to upload and execute arbitrary programs on the affected system via TCP port 443.

MitigationUpgrade to ZCM 11.2.4 or later to remediate this vulnerability. As a compensating control, network segment the affected system and restrict access to port 443 to trusted IPs only 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.3= 11.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. Confirm Novell ZENworks Configuration Management is installed
    Look for ZENworks installation directories or check system services for Novell ZENworks services. Common installation paths include C:\Novell\ZENworks on Windows or /opt/novell/zenworks on Linux.
    Affected if The product is not installed or has been removed entirely.
  2. Check the installed ZCM version number
    Use the ZENworks command line utility (zman) or check the product About/Version information in the ZENworks Control Center. The version is typically displayed in the administrative interface or can be retrieved via: zman version or similar version query commands.
    Affected if The installed version is exactly 10.3 or exactly 11.2.
  3. Verify the web server component is accessible on TCP port 443
    Attempt to reach the ZENworks web interface via HTTPS on port 443 from a remote system or locally verify the service is listening: netstat -an | findstr 443 or ss -tlnp | grep 443.
    Affected if The web interface is accessible on port 443 and responds to HTTP/HTTPS requests.
  4. Confirm the vulnerable endpoint exists
    Attempt to access the path /zenworks/jsp/index.jsp on the server over HTTPS port 443. A response (even an error page) indicates the endpoint is present.
    Affected if The /zenworks/jsp/index.jsp path is accessible and returns any response.

If the installed ZENworks Configuration Management version is exactly 10.3 or 11.2 AND the web component is running and accessible on port 443, the system is affected by this vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ZCM 11.2.4 or later to remediate this vulnerability. As a compensating control, network segment the affected system and restrict access to port 443 to trusted IPs only until the upgrade can be applied.

Recommended fix High confidence

ZENworks Configuration Management 11.2.4 or later (note: ZCM 10.3 reached end of life; migrate to 11.2.4+)

  1. Download Novell ZENworks Configuration Management 11.2.4 or later from the Novell/SUSE support portal
  2. Ensure you have a complete backup of your ZCM database and configuration
  3. Review the ZCM 11.2.4 release notes for any pre-upgrade requirements
  4. Run the ZCM upgrade installer on the primary server first
  5. After upgrading the primary server, upgrade any remaining managed devices and satellite servers
  6. Verify that the web server properly enforces authentication after upgrade
Caveat ZCM 10.3 is end-of-life; no direct upgrade path exists - migration to 11.x required; review compatibility of custom bundles and policies before upgrading

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

Fix this in Zenworks Configuration Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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