CVE-2014-6256
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 · uneditedZenoss Core through 5 Beta 3 allows remote attackers to bypass intended access restrictions and place files in a directory with public (1) read or (2) execute access via a move action, aka ZEN-15386.
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 confidenceZenoss Core through version 5 Beta 3 contains an access restriction bypass vulnerability where remote attackers can exploit the file 'move' action to place files into directories with public read or execute permissions, circumventing intended access controls.
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<= 5.0.0= 2.4.0= 2.4.5= 2.5.0= 2.5.1= 2.5.2= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 3.1.0= 3.2.0CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Zenoss Core versionCheck the installed Zenoss version by running 'zenpack --version' or inspecting '/opt/zenoss/VERSION' if it exists, or check the Zenoss web interface footer for the version numberAffected if The installed version matches any of these: 5.0.0 or lower, 2.4.0, 2.4.5, 2.5.0, 2.5.1, 2.5.2, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.1.0, or 3.2.0
-
Determine if management interface is network-accessibleCheck if the Zenoss web interface (default port 8080 or 443) is bound to a publicly accessible IP or is reachable from untrusted networks. Use 'netstat -tlnp | grep -E "(8080|443)"' to see listening addressesAffected if The Zenoss management interface is reachable from IP addresses outside the trusted administrative network
-
Verify file move functionality exposureCheck if the file move action endpoint is accessible without additional authentication layers beyond the standard Zenoss login. Inspect Zenoss event management or file handling configurations for exposed move operationsAffected if The file move functionality can be accessed by authenticated users who should not have filesystem access to public-readable directories
You are affected if your Zenoss Core version is 5.0.0 or lower, or one of the specific 2.x/3.x versions listed, AND the management interface is accessible from untrusted networks, allowing exploitation of the file move action to write to publicly-readable directories.
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 dataUpgrade Zenoss Core to a version beyond 5 Beta 3 where this vulnerability has been patched. If upgrade is not immediately feasible, restrict network access to the Zenoss management interface and audit file operation permissions.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6256 — 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-2014-6256 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