Splunk Enterprise versions 6.1.7, 6.0.8, and 5.0.12 address two vulnerabilities.
At the time of this announcement, Splunk is not aware of any cases where these vulnerabilities have been actively exploited. Previous Product Security Announcements can be found on our Splunk Product Security Portal. Use SPL numbers when referencing issues in communication with Splunk. If there is no CVE Identifier listed with a vulnerability, it will be added once it is assigned by a CVE Numbering Authority. To standardize the calculation of severity scores for each vulnerability, when appropriate, Splunk uses Common Vulnerability Scoring System version 2.
To mitigate these issues, Splunk recommends upgrading to the latest release and applying as many of the Hardening Standards from the Securing Splunk documentation as are relevant to your environment. Splunk Enterprise releases are cumulative, meaning that future releases will contain fixes to these vulnerabilities, new features and other bug fixes.
Description: OpenSSL versions prior to 1.0.1k and 0.98zd do not properly validate session parameters. These vulnerabilities could cause a Splunk instance communicating with a malicious server to not properly use ephemeral keys (CVE-2014-3572) or use weaker RSA keys (CVE-2015-0204).
CVSS Severity (version 2.0):
CVSS Base Score | 3.6 |
CVSS Impact Subscore | 4.9 |
CVSS Exploitability Subscore | 3.9 |
Overall CVSS Score | 3.6 |
Description: A path traversal vulnerability exists in Splunk Enterprise versions 6.0.x prior to 6.0.8 and 5.0.x prior to 5.0.12. This vulnerability permits an authenticated user to read arbitrary files on the host running Splunk Web.
CVSS Severity (version 2.0):
CVSS Base Score | 6.8 |
CVSS Impact Subscore | 6.9 |
CVSS Exploitability Subscore | 8.0 |
Overall CVSS Score | 6.8 |