TLS 1.3 is Coming - How to deal with it????

[Brandon_Wertz]

My security counter parts came to me letting me know that in Chrome version 70.X+ TLS 1.3 will be turned on by default.  This appears to be causing problems in our current firewall deployment:

A/P HA-par 5220s running 8.0.10 (soon to be 8.0.12).

It looks like Google has released an article describing what's going on:

https://www.chromium.org/Home/tls13

In this article it highlights how Cisco FirePower devices can be configured to avoid issue.  Does anyone know how to correct this in Palo?

Here is the error the users get (TLS1.3 Downgrade detected)

This is the traffic log for the user traffic.  "Webmail" access is allowed, and we're doing SSL decryption.

[bspilde]

This message was sent to Palo Alto Networks customers:

Dear valued Palo Alto Networks customer,

Please take the action recommended below if you have enabled SSL decryption forward proxy. This is required for users to access Gmail and other websites and applications using web browsers that implement strict TLS 1.3 compliance. We have been informed that Google Chrome is planning to implement strict TLS 1.3 compliance in their upcoming version 72. The stable build of Google Chrome version 72 may be available in January 2019, and if your users use a pre-stable build of Google Chrome, they will experience the issue outlined below earlier.

Applies to

All supported PAN-OS releases

Action Required

If you run PAN-OS 8.1:

• Upgrade to PAN-OS 8.1.4 (available now)

If you run a prior version of PAN-OS, plan to upgrade to one of the following releases:

• PAN-OS 8.0.14 (targeted to be available on Nov 15, 2018*)
• PAN-OS 7.1.21 (targeted to be available on Nov 1, 2018*)

Impact

Without upgrading to one of the above maintenance releases, users may no longer be able access Gmail and other websites and applications that utilize TLS 1.3 when SSL forward proxy decryption is in use. As a result, your users will receive the following web browser error: ‘ERR_TLS13_DOWNGRADE_DETECTED’.

By upgrading PAN-OS to one of the above maintenance releases, your users will be able to continue to access Gmail and other TLS 1.3 enabled websites and applications when using browsers that exhibit this behavior.

[Brandon_Wertz]

---

@bspilde wrote:

PAN-OS 8.0.14 and 8.1.4 will support TLS 1.3.

---

Thanks for following up.

[Brandon_Wertz]

@bspilde Where / How did you recieve this info below?

---

@bspilde wrote:

This message was sent to Palo Alto Networks customers:

Dear valued Palo Alto Networks customer,

Please take the action recommended below if you have enabled SSL decryption forward proxy. This is required for users to access Gmail and other websites and applications using web browsers that implement strict TLS 1.3 compliance. We have been informed that Google Chrome is planning to implement strict TLS 1.3 compliance in their upcoming version 72. The stable build of Google Chrome version 72 may be available in January 2019, and if your users use a pre-stable build of Google Chrome, they will experience the issue outlined below earlier.

Applies to

All supported PAN-OS releases

Action Required

If you run PAN-OS 8.1:

• Upgrade to PAN-OS 8.1.4 (available now)

If you run a prior version of PAN-OS, plan to upgrade to one of the following releases:

• PAN-OS 8.0.14 (targeted to be available on Nov 15, 2018*)
• PAN-OS 7.1.21 (targeted to be available on Nov 1, 2018*)

Impact

Without upgrading to one of the above maintenance releases, users may no longer be able access Gmail and other websites and applications that utilize TLS 1.3 when SSL forward proxy decryption is in use. As a result, your users will receive the following web browser error: ‘ERR_TLS13_DOWNGRADE_DETECTED’.

By upgrading PAN-OS to one of the above maintenance releases, your users will be able to continue to access Gmail and other TLS 1.3 enabled websites and applications when using browsers that exhibit this behavior.

---

[bspilde]

It was sent via email from noreply@paloaltonetworks.com on October 22nd. I’m not sure exactly what enrolled me in the message list.

On the support page check preferences under your profile for all communication preferences by type.

Hope that helps!

[elangeland]

This issue had disappeared for us after upgrading our firewalls (now at 8.1.5). However, as of this morning (on Chrome 71.0.3578.98 and possibly older versions), it has reappeared for at least two URLs:

https://www.yegjoyride.com/volunteer-1

https://eschenker.dbschenker.com//nges-portal/public/en-US_US/#!/tracking/customer-search?refType=aa...

The first one is happy in Firefox; however, the second one has a similar error in Firefox. No errors occur from our guest network, which has no decryption.