Splunk 6.0.1 addresses one vulnerability

Description

Splunk version 6.0.1 addresses the following vulnerability:

• Malformed network input crashes Splunk Enterprise (SPL-75668, CVE-2013-7337)

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:

• SPL-75668: Only affects Splunk Enterprise 6.0 components configured as data “receivers” on the listening or receiving port(s). This impacts Splunk Enterprise instances configured as indexers and any forwarders configured as intermediate forwarders.

  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 Vincent Kéravec EVRY ASA with the responsible disclosure of this issue.

Vulnerability Descriptions and Ratings

Malformed network input crashes Splunk (SPL-75668, CVE-2013-7337)

Description: A Denial of Service (DoS) vulnerability was identified in Splunk Enterprise. An attacker can send a malformed packet, causing the Splunk server to be unavailable.

CVSS Severity (version 2.0):

CVSS Base Score 7.8

CVSS Impact Subscore 6.9

CVSS Exploitability Subscore 10

Overall CVSS Score 7.8

Document History

• 2013-Dec-17: Rev 1. Initial Release
• 2014-Mar-25: Rev 2. Assigned CVE