icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Heartbleed Command for Splunk
SHA256 checksum (heartbleed-command-for-splunk_12.tgz) 24dbb2cd1a53460c213a8108c69da082d4399a03848ed175b89d6ba118923b84 SHA256 checksum (heartbleed-command-for-splunk_11.tgz) 5d6b44f76bde4fca310336b5f3c3dcc3962b56d4feea871ded5bbd186bfd310c SHA256 checksum (heartbleed-command-for-splunk_10.tgz) a289bdc363afacfca774b407e49a121dcc9072f62be63cfb40182a05fa7fbc5f
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Heartbleed Command for Splunk

Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
A Splunk command named heartbleedtest, developed by Discovered Intelligence (DI), that can be used to check your internal infrastructure and external websites for the Heartbleed vulnerability.

A Splunk heartbleedtest command

This CIM-Compliant Technology Add-on (TA-Heartbleed) contains a new heartbleedtest command that can be used to check your internal infrastructure and external websites for the recently announced Heartbleed vulnerability.

Upon invoking the command on your Splunk search results, it will run a check against provided host/port values and return a new field, named vulnerable, that will state whether the host values are vulnerable to heartbleed or not.

How to use the command

The command is invoked as follows:

| heartbleedtest serverfield=[serverfield] portfield=[portfield] timeout=[int] poolsize=[int]

Note: fieldvalue, port, timeout and poolsize are optional.
Here are the defaults when they are not specified:
serverfield = dest
portfield = port
timeout = 3
poolsize = 10

  • The serverfield field contains host values (e.g. google.com, yahoo.com, myserver.company.com)
  • The portfield contains port numbers (e.g. 443, 8000)
  • Timeout is declared as an integer
  • Poolsize is declared as an integer and represents how many concurrent threads are launched with the command. For example, the default poolsize of 10 will allow for 10 hosts to be checked by the command at once, whereas a poolsize of 100 will allow 100 hosts to be checked at once.

NOTE: Use caution with the poolsize. The greater the poolsize, the more memory is used. A poolsize of 100 seems to be a nice sweetspot, but if you go higher, please use caution.

Example searches

MySplunkSearch | heartbleedtest serverfield=dest portfield=port timeout=3 poolsize=10 | table dest port vulnerable

These are actually the default variables and we do not actually need to declare them – we are doing so here for illustrative purposes. This will run the heartbleed test on using the default serverfield of dest, the default portfield of port, the default timeout of 3 seconds and the default poolsize of 10. It will tabulate the results and tell you if any dest values are vulnerable.

MySplunkSearch | heartbleedtest serverfield=myHostField portfield=myPortField timeout=10 poolsize=100 | table myHostField myPortField vulnerable

This will run the heartbleed test on a serverfield of myHostField, a portfield of myPortField, a timeout of 10 seconds and a poolsize of 100. It will tabulate the results and tell you if any myHostField values are vulnerable.


To install the command – download the TA, then install into Splunk as you would do any other app and you should be all set. The command is set to be global, so should work from any of your existing apps.

Sample Dashboard

We have knocked up a quick Heartbleed Checker dashboard form that allows you to leverage the command on a nice form in Splunk to check hosts/ports individually and get the results back. You should just be able to copy and paste into an empty view/dashboard. Feel free to edit where you see fit.

    <label>Heartbleed Checker</label>
    <fieldset autorun"false"="" submitbutton="true">
    <input type="text" token="dest">
    <input type="text" token="port">
    <input type="text" token="timeout">
        <title>Heartbleed Results</title>
        <searchstring>index=_* earliest=-60m | head 1 | eval port="$port$" | eval timeout="$timeout$" | eval dest="$dest$" | heartbleedtest | table dest port vulnerable</searchstring>

For support, feedback, questions, concerns – feel free to contact us.

Looking to expedite your success with Splunk? Click here to view the Splunk service offerings that Discovered Intelligence offers.

Release Notes

Version 1.2
April 25, 2014

Version 1.2
- Added in new poolsize variable that allows for concurrent checking of hosts
- New Socket error message if no connection possible

Our thanks to Kenichi Suda (Macnica Networks Corp. based in Japan) for his help with these new enhancements!

Version 1.1
April 11, 2014

Release 1.1 - Minor bug fix

Version 1.0
April 11, 2014

Release 1.0


Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2019 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.