CVE-2015-0785
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 · uneditedcom.novell.zenworks.inventory.rtr.actionclasses.wcreports in Novell ZENworks Configuration Management (ZCM) allows remote attackers to read arbitrary folders via the dirname 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 confidencePath traversal vulnerability in the wcreports component of Novell ZENworks Configuration Management allows remote unauthenticated attackers to read arbitrary folders on the file system via manipulation of the dirname variable.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify ZCM installation existsCheck for ZENworks Configuration Management by looking for its installation directory (typically at /opt/novell/zenworks or C:\Program Files\Novell\ZENworks) or by querying installed packages/services for 'zenworks' or 'ZCM'Affected if ZENworks Configuration Management software is installed on the system
-
Confirm wcreports component is accessibleAttempt to access the wcreports endpoint on the ZCM web server (typically at /wcreports or /wcreports/) via HTTP/HTTPS request from the server itself or check if the endpoint respondsAffected if The wcreports web component is exposed and responds to requests (this component is built into ZCM and present in all versions)
-
Check ZCM versionRun the ZCM version command: on Linux/Unix '/opt/novell/zenworks/bin/zenworks --version' or check the about page in the ZCM web console, or examine the installed package version via the system package managerAffected if Any installed version of Novell ZENworks Configuration Management is present (all versions are affected per the CVE)
-
Verify network accessibility of ZCM web interfaceCheck if the ZCM web server ports (typically 443 or 8443) are listening on network interfaces accessible to unauthenticated users using 'netstat -an | grep -E '(443|8443)' or similar network scanning toolsAffected if The ZCM web interface including wcreports is accessible from untrusted networks
If Novell ZENworks Configuration Management is installed with the wcreports component accessible over the network, the system is affected by CVE-2015-0785 since all versions are vulnerable to unauthenticated path traversal via the dirname parameter.
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 dataApply the vendor patch for CVE-2015-0785 or upgrade to a patched ZCM version; restrict network access to the affected ZCM web interface if patching is delayed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0785 — 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-0785 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