OpenSSL Heartbleed bug: CVE-2014-0160

Reply
L4 Transporter

Re: OpenSSL Heartbleed bug: CVE-2014-0160

Palo Alto has just released threat and content version 430

L1 Bithead

Re: OpenSSL Heartbleed bug: CVE-2014-0160

yes, and I've just applied it and still the same. No entries in threat log for threated 36416 when doing vulnerability tests with all available online tools.

L2 Linker

Re: OpenSSL Heartbleed bug: CVE-2014-0160

Are you performing SSL inspection? Still trying to work out if this is required to catch this vulnerability with IPS... Depends if it happens inside an establish TLS tunnel or in clear text I suppose?

L4 Transporter

Re: OpenSSL Heartbleed bug: CVE-2014-0160

This does not require to have inbound SSL inspection in place. The vuln is detected during SSL negotiation.

L4 Transporter

Re: OpenSSL Heartbleed bug: CVE-2014-0160

I guess the targeted host must have a vulnerable version of openssl installed to trigger one of the four TP signatures. At least I cannot trigger an alert with 430 installed against a non vulnerable host. Makes sense somehow...

L2 Linker

Re: OpenSSL Heartbleed bug: CVE-2014-0160

Thank you!

Got it all working perfectly now at several locations. I also created a custom rule to block/drop those medium severity signatures in the latest update, this results in the online tests failing too (malformed response) to give clients some extra peace of mind.

Seeing a large number of IPs from China trying to exploit this!

Several days of replacing SSL certificates ahead of me now!

L4 Transporter

Re: OpenSSL Heartbleed bug: CVE-2014-0160

Good luck !

L0 Member

Re: OpenSSL Heartbleed bug: CVE-2014-0160

davido140 wrote:

Thank you!

Got it all working perfectly now at several locations. I also created a custom rule to block/drop those medium severity signatures in the latest update, this results in the online tests failing too (malformed response) to give clients some extra peace of mind.

Seeing a large number of IPs from China trying to exploit this!

Several days of replacing SSL certificates ahead of me now!

What parameters did you use to trigger this rule?  I'm not seeing any way to trigger on a threat ID or anything like that.:smileyconfused:

L2 Linker

Re: OpenSSL Heartbleed bug: CVE-2014-0160

Just used heartbleed in the threat name on the rule in the Vuln' protection profile and set the action to block

This forces traffic to be dropped for the "medium" severity threats related to heartbleed in the 430 update.

Effect from one of the online tests will be a timeout and you'll get an event in the threat log.

The target system MUST be vulnerable to trigger these signatures, if you've already patched it you wont see anything in the logs.

L4 Transporter

Re: OpenSSL Heartbleed bug: CVE-2014-0160

I cannot get the 430 update to download it failed

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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 Live Community as a whole!

The Live Community thanks you for your participation!