CVE-2014-6255
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 · uneditedOpen redirect vulnerability in the login form in Zenoss Core before 4.2.5 SP161 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via the came_from parameter, aka ZEN-11998.
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 confidenceOpen redirect vulnerability in Zenoss Core's login form. The came_from parameter is not validated before being used in a redirect, allowing attackers to specify arbitrary external URLs that users are redirected to after authentication, facilitating phishing attacks.
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<= 4.2.5= 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
- None
AV:N/AC:L/Au:N/C:P/I:P/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 Zenoss Core installationRun 'rpm -qa | grep -i zenoss' or check for Zenoss installation directory (typically /opt/zenoss)Affected if Zenoss Core is not installed on the system
-
Identify installed Zenoss versionCheck the version file: 'cat /opt/zenoss/version.txt' or run 'rpm -qa | grep -i zenoss-core' to list installed Zenoss packagesAffected if The installed version matches <= 4.2.5 OR equals any of: 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
-
Confirm web interface is accessibleAttempt to access the Zenoss login page via HTTP/HTTPS (default port 8080): visit http://localhost:8080/zport/dmd or the configured login URLAffected if The Zenoss login form is reachable and the came_from parameter can be manipulated
-
Test for unvalidated redirect (optional)Submit a login request with a came_from parameter pointing to an external domain: POST to /zport/acl_login with came_from=http://attacker.com, then verify if redirection occurs to the external URL after authenticationAffected if After login, the user is redirected to the external URL specified in came_from rather than being restricted to internal paths
If Zenoss Core version is <= 4.2.5 or matches any of the listed specific versions (2.4.x, 3.0.x-3.2.x) and the web interface is accessible, the environment is likely affected by this open redirect vulnerability.
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 4.2.5 SP161 or later which implements proper validation of the came_from parameter to restrict redirects to trusted internal paths only.
- 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-6255 — 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-6255 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