Splunk 5.0.5 addresses one vulnerability

Description

Splunk version 5.0.5 addresses the following vulnerability:

• Abuse of a test script mechanism to execute shell code (SPL-70250, CVE-2013-6771)

At the time of this announcement, Splunk is not aware of any cases where this vulnerability has 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 the 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.

Affected Products and Components

Security vulnerability addressed by this maintenance release affects the following version(s):

• SPL-70250: Splunk 5.0.4 and all older versions

  Mitigation and Upgrades

  To mitigate this issue, 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 releases are cumulative, meaning that future releases will contain fixes to these vulnerabilities, new features and other bug fixes.

Credit

Splunk would like to thank and credit Gerhard Muntingh and CyberCrown Ltd working with HP’s Zero Day Initiative with the responsible disclosure of this issue.

Vulnerability Description and Rating

Abuse of a test script mechanism to execute shell code (SPL-70250, CVE-2013-6771)

Description: Several scripts provided with Splunk for system operators to test and troubleshoot alert scripts were removed from the software package to prevent the possibility that an authenticated Splunk user could abuse them in order to construct and execute an arbitrary shell script on the Splunk host.

CVSS Severity (version 2.0):

CVSS Base Score 8.5

CVSS Impact Subscore 10

CVSS Exploitability Subscore 6.8

Overall CVSS Score 7

Document History

• 2013-Sep-23: Rev 1. Initial Release
• 2014-Mar-10: Rev 2. Included CyberCrown Ltd working with HP’s Zero Day Initiative