Splunk Product Security Portal

OpenSSL Vulnerability (CVE-2014-3511), August 14th, 2014:

All supported Splunk Enterprise versions are affected and we are actively working on fixing and testing Maintenance Releases to include updated versions of OpenSSL. The impact is an attacker could force a TLS connection to downgrade to TLS 1.0 even if higher versions are supported by the client and server. Please stay tuned for the next maintenance updates and a more detailed security announcement.

How to Report a Splunk Vulnerability

About this Portal

The Splunk Product Security Portal serves as the authority for the following:

Subscribe to our RSS feed to be alerted of new announcements.

Splunk Product Security Announcements

September 3, 2014:Splunk Enterprise 6.0.6 addresses two vulnerabilities
August 4th, 2014:Splunk Enterprise 6.1.3 addresses two vulnerabilities
July 1st, 2014:Splunk Enterprise 6.1.2, 6.0.5 and 5.0.9 address two vulnerabilities (CCS Injection)
May 9th, 2014:Splunk Enterprise 6.0.4 addresses one vulnerability
April 10th, 2014:Splunk Enterprise 6.0.3 addresses two vulnerabilities (Heartbleed)
March 25th, 2014:Splunk Enterprise 5.0.8 addresses one vulnerability
December 17th, 2013:Splunk Enterprise 6.0.1 addresses one vulnerability
November 20th, 2013:Splunk Enterprise 5.0.6 addresses one vulnerability
September 23rd, 2013:Splunk Enterprise 5.0.5 addresses one vulnerability
July 29th, 2013:Splunk Enterprise 5.0.4 addresses one vulnerability
May 28th, 2013:Splunk Enterprise 5.0.3 addresses multiple vulnerabilities
March 25th, 2013:Splunk Enterprise 4.3.6 addresses one vulnerability
November 16th, 2012:Splunk Enterprise 4.3.5 and 5.0 address three vulnerabilities
November 1st, 2012:Splunk Enterprise 5.0 addresses two vulnerabilities
March 5th, 2012:Splunk Enterprise 4.3.1 addresses one vulnerability
December 12th, 2011:Splunk Enterprise 4.2.5 addresses three vulnerabilities
October 19th, 2011:Splunk Enterprise 4.2.4 addresses two vulnerabilities
August 9th, 2011:Splunk Enterprise 4.2.3 addresses two vulnerabilities
June 15th, 2011:Splunk Enterprise 4.2.2 addresses one vulnerability
April 18th, 2011:Splunk Enterprise 4.2.1 addresses one vulnerability
February 10th, 2011:Splunk Enterprise 4.1.7 addresses five vulnerabilities
December 1st, 2010:Splunk Enterprise 4.1.6 addresses one vulnerability
September 9th, 2010:Splunk Enterprise 4.1.5 addresses two vulnerabilities
June 7th, 2010:Cross-site Scripting in Splunk Web with 404 Responses in Internet Explorer
May 10th, 2010:Vulnerability in Example PAM Authentication Script
May 3rd, 2010:Splunk Enterprise Critical Maintenance Release and Patch

Splunk Product Security Policy

Evaluation:

Splunk maintains a policy of evaluating all potential security vulnerabilities that are discovered internally or externally within 48 hours of discovery.

Splunk uses the Common Vulnerability Scoring System Version 2 to rate vulnerabilities. CVSSv2 is an industry-standard rating system for security incidents. Scores are calculated using the best available analysis and metrics and are included in all vulnerability announcements.

Fixing:

Splunk maintains the following policy of responsible vulnerability fixing:

  • Splunk releases, including maintenance, minor and major releases, will include cumulative fixes for vulnerabilities that are found, verified and able to be fixed within the timeframe of the release.
  • Splunk will issue releases to fix vulnerabilities for all applicable and supported versions.
  • In the case of critical risk, high impact vulnerabilities, Splunk will make all reasonable effort to expedite maintenance releases for all affected versions.
  • In the case of critical risk, high impact vulnerabilities, Splunk will make all reasonable effort to supply patches, assuming that patches are a viable stop-gap for customers who cannot otherwise upgrade Splunk.

Disclosure

Splunk maintains the following policy of responsible disclosure:

  • Splunk will announce vulnerabilities via www.splunk.com/prodsec and Splunk Product Security Announcements RSS feed.
  • Splunk will not publicly announce security vulnerabilities until fixes are publicly available.
  • For critical risk, high impact vulnerabilities, Splunk may contact customers that are especially vulnerable in order to recommend mitigations in the case that a fix is not yet available.
  • Splunk will not release the exact details of vulnerabilities.

Splunk Product Security Best Practices

Harden all Splunk Instances per Splunk Hardening Standards

Application of some or all of the Splunk Hardening Standards, which are located in the Securing Splunk manual, will help mitigate the risk and impact of most vulnerabilities.

Subscribe to our product security RSS feed

Our RSS feed contains all official product security announcements, and is updated as soon as an announcement is released.

Per the Splunk Product Security Policy, someone will be in touch with you within 48 hours of receipt of your communication.