Splunk® Enterprise

Securing the Splunk Platform

Acrobat logo Download manual as PDF


Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
Acrobat logo Download topic as PDF

Avoid unintentional execution of fields within CSV files in third party applications

When you run a search on the Splunk platform, you can export those results as a comma separated values (CSV) file. If you then later open this file in an application like Microsoft Excel or Apache OpenOffice, any fields that are in the CSV file can execute within those applications.

Take the following example:

  1. On the Splunk platform, you run the following search:

    stats count | eval trick ="=1+1"

  2. You export the results as a CSV file.
  3. You then open the file in Microsoft Excel.
  4. Because the CSV file has a field "=1+1", Excel calculates that field and gets the result of 2.

To avoid this problem, you can do one of the following:

  • Edit the CSV file using a text editor before you import the file into Excel or OpenOffice. For any field in the file that begins with the following characters, add a space to the beginning of and remove any tab characters (0x09) within the field:
    • =
    • -
    • "
    • @
    • +
  • Append any field that starts with the previously listed characters with an apostrophe (').
  • On the Splunk platform, confirm that users do not hold a role that has the "export_results_is_visible" capability. This capability displays the "Export results" button in the search results window. You cannot generate CSV files at all if you do not hold a role that has this capability.
Last modified on 09 February, 2021
PREVIOUS
Manage data integrity 		  NEXT
How to self-sign certificates

This documentation applies to the following versions of Splunk® Enterprise: 6.3.0, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.10, 7.0.11, 7.0.13, 6.3.1, 7.0.3, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.2.0, 8.2.1, 7.0.4

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters