04-07-2014 10:35 PM
Just wondering if any Palo Alto versions are affected by this bug in OpenSSL?
04-09-2014 08:08 AM
Yes, it looks to have just went live. Any reason as to why it was originally pulled and then re-released?
04-09-2014 08:15 AM
Initially there was an issue, the newly added signature was not visible until the user logout and login again into the GUI.
04-09-2014 08:16 AM
I have applied it but when we test our websites using Test your server for Heartbleed (CVE-2014-0160) it reports our sites as vulnerable.
04-09-2014 08:18 AM
So this update can be installed during work hours and not cause any issues to the operation of the PA
04-09-2014 08:23 AM
Is that a question? If it is the answer is yes.
04-09-2014 08:25 AM
rgreens, mine is doing the same thing still. Is the update not working?
04-09-2014 08:26 AM
rgreens, Are you seeing the vulnerability signature firing in the Threat Log? When we try either that website or the Python script that is going around against our websites, I do not see anything in the Threat log after we have applied 429-2164.
04-09-2014 08:30 AM
Nothing in the threat log either.
04-09-2014 08:35 AM
I'm using ssltest.py to test various sites both behind a pair of PA firewalls and internal sites where traffic is monitored by a PA4020 in tap mode only, and I can't get the threat alert to fire off when I test sites. Is anyone else having trouble verifying the threat rule is working?
For reference I'm using ssltest.py from here:
04-09-2014 11:55 AM
I was not able to get the signature to fire neither....
04-09-2014 12:46 PM
Has anyone actually gotten hit by heartbleed? If so how does it show in the PA etc.
04-09-2014 01:17 PM
Is this it?
Threat/Content Name OpenSSL TLS Heartbeat Information Disclosure Vulnerability
04-09-2014 01:21 PM
IPS vulnerability signature ID 36416 ("OpenSSL TLS Heartbeat Information Disclosure Vulnerability")
04-09-2014 01:25 PM
I think you guys were searching for the wrong thing. It was there all along
04-09-2014 01:57 PM
For good measure, I deleted the existing Threat Definitions and pulled down new ones as I thought perhaps I had originally installed the version that had been pulled by engineering.
Still can't get it to recognize threat hits.
Will this signature/SSL Decoder only work in a situation where the PA is performing decryption?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!