Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

RSA TLS crypto attack, ROBOT—short for "Return Of Bleichenbacher's Oracle Threat

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

RSA TLS crypto attack, ROBOT—short for "Return Of Bleichenbacher's Oracle Threat

L2 Linker

Recent article talks about a newly discovered (but old) vulnerability: 

     https://arstechnica.com/information-technology/2017/12/a-worrying-number-of-sites-remain-open-to-maj...

 

You can test your links here if you are vulnerable: 

     https://robotattack.org 


With TLSv1.2, all my Palo Alto GlobalProtect interfaces check as vunerable.
Has anyone heard of this and is there a configuration that lessen the vulnerability?


Thank you.

9 REPLIES 9

L1 Bithead

Hi,

 

Same issue there. All our GlobalProtect portals seems to be vulnerable even with the latest PANOS revision.

I've noticed that It only affects GlobalProtect portals bound with SSL certificates which do use the RSA algorithm.

 

The US-Cert has recently published an advisory: http://www.kb.cert.org/vuls/id/144389

 

Any advice would be appreciated.

 

Many thanks.

Hi, thanks for that link to the US-Cert alert. I was thinking that maybe the SSL certificate is the issue, but we have the same type of certificate on our Juniper\Pulse VLN interface, and that doesn't report vulnerable.


I think most of us use the RSA type of certificate, as not all vendor issue ECC/ECDSA certificates, and maybe some issue with older browsers not supporting it. I like this site on it: https://wiki.mozilla.org/Security/Server_Side_TLS 

Hi FRVSA,

I've just got a confirmation from PA tech support:
"The PAN-OS is vulnerable and they are currently working towards a fix which prevents the attacker to exploit this vulnerability.
Currently they do not have a release timeline and this is currently marked as the highest priority possible. They are also working on determining if this will be a hot patch or released in an OS update."

I do appreciate the honesty from PA tech support, and I hope the fix is out soon.

Hi Curtis,

 

Many thanks for your feedback and for having contacted the support!

 

That clarifies the situation 🙂

Good to see that Palo is working on a fix.

 

You right I agree and appreciate as well their honesty.

 

Thanks again and see you on the community threads.

 

 

Please note that we have posted the following advisory regarding ROBOT.

 

https://live.paloaltonetworks.com/t5/Threat-Vulnerability-Articles/PAN-OS-exposure-to-ROBOT-attack/t...

Hi Curtis - any idea if this fix will resolve findings on Global Protect portals using an RSA cert? Seems this mitigation / workaround statement only reflects fixes on the SSL Decryption Profiles.

 

https://securityadvisories.paloaltonetworks.com/Home/Detail/117

 

L2 Linker

Hi Scotty,

The 757 contect update is giving some extra protection, but doesn't solve the problem.
I've done the update and our GP site still tests vulnerable. 
Their jugestion of switching to DHA type certificate is not an option for me at this time.

It seems to me that they are coming out with an actual fix, with 8.0.7: 

https://www.paloaltonetworks.com/documentation/80/pan-os/pan-os-release-notes/pan-os-8-0-7-addressed...

 

PAN-89936
A security-related fix was made to prevent the decryption of captured sessions through the ROBOT attack (CVE-2017-17841).

 

But I haven't tested it yet.

 

Margit

Hi Margit,

 

Same thing here - 757 has the signature and can be applied to a vulnerability protection profile, but external facing portals will still show the finding. We're running PanOS 7.1.11 and PanOS 8.0.7 is not an option for us at this time. 

 

They did update the mitigation notes to reflect issues with PanOS 7.1, but it's not clear.

 

Scott

Hi Everyone,

 

PANOS- 7.1.15 is out and the release note includes the following entrie:

 

PAN-89936: A security‐related fix was made to prevent the decryption of captured sessions through the ROBOT attack (CVE‐2017‐17841).

 

I assume it solves the vulnerability exposition but not tested yet.

 

Cheers.

  • 13328 Views
  • 9 replies
  • 2 Likes
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!