Vulnerability Note VU#449452
Zenoss Core contains multiple vulnerabilities
Original Release date: 05 Dec 2014 | Last revised: 08 Dec 2014
The Zenoss Core application, server, and network management platform software contains multiple vulnerabilities, the most severe of which could allow a remote attacker to execute arbitrary code.
The Zenoss Core application, server, and network management platform software version 4.2.4 contains a collection of vulnerabilities that impacts several aspects of the software. A brief summary of the types of vulnerabilities present is provided below.
CVE-2014-6253: Systemic Cross Site Request Forgery
CVE-2014-6254: Systemic Stored Cross-Site Scripting in Zenoss Attributes
CVE-2014-6254: Cross Site Scripting from Exposed Helper Methods
CVE-2014-6255: Open Redirect in Login Form
CVE-2014-6256: Authorization Bypass Allows Moving Arbitrary Files
CVE-2014-6257: Systemic Authorization Bypasses
CVE-2014-6258: Denial of Service from User-Supplied Regular Expression
CVE-2014-6259: Denial of Service via XML Recursive Entity Expansion ("Billion Laughs")
CVE-2014-6260: Page Command can be Edited Without Password Re-Entry
CVE-2014-6261: Remote Code Execution via Version Check
CVE-2014-6262: Denial of Service via RRDtool Format String Vulnerability (this vulnerability is due to RRDtool)
CVE-2014-9245: Stack Trace Contains Internal URLs and Other Sensitive Information
CVE-2014-9246: Cross-Site Request Forgery Leads to ZenPack Installation
CVE-2014-9246: Sessions Do Not Expire
CVE-2014-9247: User Enumeration via User Manager
CVE-2014-9248: No Password Complexity Requirements
CVE-2014-9249: Exposed Services in Default Configuration
CVE-2014-9250: Cookie Authentication is Insecure
CVE-2014-9251: Weak Password Hashing Algorithm
CVE-2014-9252: Plaintext Password Stored in Session on Server
For more details, please see this spreadsheet, specifically the "Impact Description" column. Included in the linked spreadsheet are Zenoss tracking numbers for each issue.
The CVSS score below is based on CVE-2014-9246.
The most severe issues (CVE-2014-6261 and CVE-2014-9246) allow remote code execution and installation of arbitrary packages, allowing full compromise of the system running Zenoss. For more details, please see this spreadsheet, specifically the "Impact Description" column.
Apply an update manually
CVE-2014-6255 and CVE-2014-9246 (Sessions Do Not Expire) are resolved in the latest Zenoss Core 4.2.5 SP. Manually download the update as described below ("Disable automatic update check"), and apply the update as soon as possible.
Zenoss plans for most of the rest of the issues to be addressed in a future maintenance release of Zenoss Core 5.
For more information, please see this spreadsheet; specifically the "Vendor Status" column which provides the vendor’s response for the issue, and the "Zenoss Bug ID" column which provides Zenoss’s internal tracking number for the issue.
CVE-2014-9250 can be mitigated by enabling SSL/HTTPS to better protect cookie-based authentication data. Please see Zenoss’s recommendation in this spreadsheet.
Disable automatic update check
CVE-2014-6261 can be mitigated by unchecking "Check For Updates" in the Zenoss Versions page in the web interface. Note that you can also manually check for updates in the web interface, which triggers the same actions, and is therefore also vulnerable. Instead, users should check the Zenoss website for new versions, rather than using the in-app check. To avoid CSRF exploitation, users should also use a separate browser (or profile) for Zenoss, that is not shared with any other browsing.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedZenossAffected12 Nov 201403 Dec 2014If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to Ryan Koppenhaver and Andy Schmitz of Matasano Security for reporting these vulnerabilities.
This document was written by Garret Wassermann.
05 Dec 2014
Date First Published:
05 Dec 2014
Date Last Updated:
08 Dec 2014
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.