Does PRTG offer a way to monitor for the heartbleed leak?
Is it possible to monitor for the Heartbleed leak using PRTG?
Modified on 2025-08-29 15:07:10 +0200
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
This article applies to PRTG Network Monitor 14 or later, as well as to previous (deprecated) versions
Checking Websites for the Heartbleed Leak
You can use a simple Python script written by Jared Stafford to test your websites for the Heartbleed vulnerability.
Requirements
Set Up Monitoring for Heartbleed
Note: The path in the wrapper might have to be changed to point to the EXE folder on your system.
You now will get the output VULNERABLE or NOT VULNERABLE as a message for your sensor. The value is either 0 or 1, so you can work with channel limits to define error states.
Important notice: This is only a quick workaround and only port 443 is checked. This is considered an 'ad hoc' sensor and does not come with actual technical support.
Apr, 2014 - Permalink