CVE-2014-6260
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 does not require a password for modifying the pager command string, which allows remote attackers to execute arbitrary commands or cause a denial of service (paging outage) by leveraging an unattended workstation, aka ZEN-15412.
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 confidenceZenoss Core through version 5 Beta 3 lacks authentication enforcement when modifying the pager command string configuration. An attacker with physical or terminal access to an unattended workstation can inject arbitrary commands into the pager configuration, leading to remote command execution on the Zenoss server or denial of service through paging system disruption.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Check Zenoss Core versionRun 'zenpack --version' or check the Zenoss installation to identify the installed version numberAffected if The installed version is 5.0.0 or earlier, or matches any of these: 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.0
-
Identify pager configuration access pointLocate the Zenoss configuration interface for pager settings - typically found in the web UI under Settings > Pager or similar configuration sectionAffected if The pager configuration interface is accessible without requiring authentication credentials
-
Verify pager command string configurationInspect the current pager command string setting in the Zenoss configuration - look for the command that controls paging system executionAffected if The pager command string can be modified without authentication or contains unexpected/injected commands
-
Test for authentication requirementAttempt to access or modify the pager command configuration using an unauthenticated session or requestAffected if Changes to the pager configuration can be made without providing valid authentication credentials
You are affected if your Zenoss Core version is 5.0.0 or earlier (including the specific versions 2.4.0 through 3.2.0 listed) AND the pager command configuration is accessible or modifiable without authentication.
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 to Zenoss Core version 5 or later which contains the fix. Additionally, enforce session timeouts and monitor for unauthorized access to management interfaces.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2014-6260 — 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-6260 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