dbcve.org
Zenworks Configuration ManagementApplication · Novell

CVE-2015-0784

HIGH · 7.5 CVSS v3.0 Published 2017-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Rtrlet.class in Novell ZENworks Configuration Management (ZCM) allows remote attackers to obtain Session IDs of logged in users via a value of ShowLogins for the maintenance variable.

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 · moderate confidence

The vulnerability exists in Rtrlet.class in Novell ZENworks Configuration Management, where improper handling of the maintenance parameter allows attackers to inject the ShowLogins value and retrieve Session IDs of currently logged-in users. This information disclosure enables session hijacking attacks where attackers can impersonate legitimate authenticated users.

MitigationImplement strict input validation on the maintenance parameter in Rtrlet.class and add proper authorization checks to prevent unauthenticated or unauthorized access to session information. Consider implementing additional session security mechanisms such as HTTP-only cookies and regenerating session IDs on authentication.

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:all versions

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Confirm ZENworks Configuration Management installation
    Check for ZENworks installation by looking for the product in Windows Add/Remove Programs, or by searching for ZENworks-related directories and services on the system.
    Affected if The product is installed and running.
  2. Locate the vulnerable Rtrlet.class component
    Search for Rtrlet.class in the ZENworks installation directory, typically under the web tier or servlet container paths such as [ZENworks_install]/share/tomcat/webapps or similar web application directories.
    Affected if The Rtrlet.class file exists in the ZENworks web application path.
  3. Verify web interface exposure
    Check if the ZENworks web portal or admin console is accessible over the network by accessing the typical URLs such as https://[server]:443/zenworks or http://[server]:8080/zenworks.
    Affected if The ZENworks web interface is accessible without proper authentication or from untrusted networks.
  4. Test for vulnerable maintenance parameter
    Send a crafted HTTP request to the Rtrlet endpoint with the maintenance parameter set to ShowLogins, for example: GET /Rtrlet?maintenance=ShowLogins or similar path to the servlet. Compare the response against expected behavior.
    Affected if The parameter can be manipulated to reveal session information or user login data without proper authorization.
  5. Review access logs for exploitation attempts
    Examine ZENworks web server access logs and application logs for patterns containing 'maintenance' parameter with 'ShowLogins' value, or for unexpected session disclosure.
    Affected if Logs show requests with maintenance=ShowLogins or similar patterns that indicate probing or exploitation of this vulnerability.

If ZENworks Configuration Management is installed and its web interface is accessible, the environment is potentially affected because all versions of this product contain the vulnerable Rtrlet.class component.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the maintenance parameter in Rtrlet.class and add proper authorization checks to prevent unauthenticated or unauthorized access to session information. Consider implementing additional session security mechanisms such as HTTP-only cookies and regenerating session IDs on authentication.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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