SSH protocol uses Weak key exchange algorithms in PA 500 for PAN OS 8.1.14

Reply
Highlighted
L1 Bithead

SSH protocol uses Weak key exchange algorithms in PA 500 for PAN OS 8.1.14

Hi Team ,

  PA 500 with 8.1.14 (latest OS )  is having the Vulnerability SSH protocol uses Weak key exchange algorithms. I understand we can change algorithm values with set deviceconfig system ssh kex  to stronger algorithm post 9.0 unfortunately PA 500 do not have 9.0 release in software download.

So how do we close this one , is there any alternative way we can change Kex values , or else we need  to compromise with this Vulnerability.

 

Truth is a pathless land, and you cannot approach it by any path whatsoever
Highlighted
L7 Applicator

Re: SSH protocol uses Weak key exchange algorithms in PA 500 for PAN OS 8.

If you do not expose your management interface to an untrusted network (make it accessible inside MGMT network, set an ACL,..) you will be able to mitigate most exposure

If you must make the interface available, ensure connections need to traverse the firewall so you can apply security profiles to the connection

reaper - PANgurus.com
I drink and I know things
Highlighted
L1 Bithead

Re: SSH protocol uses Weak key exchange algorithms in PA 500 for PAN OS 8.

TAC Engineer is suggesting to change the Firewall mode into FIPS-CC. Is it viable to change the Firewalls which are in production to FIPS-CC to mitigate this Vulnerability.

Truth is a pathless land, and you cannot approach it by any path whatsoever
Highlighted
Cyber Elite

Re: SSH protocol uses Weak key exchange algorithms in PA 500 for PAN OS 8.

Hello,

You might want to read up on what is truly disabled via FIPS mode. Also here is an article on disabling weak ciphers.

 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMNPCA4

 

Cheers!

Highlighted
L6 Presenter

Re: SSH protocol uses Weak key exchange algorithms in PA 500 for PAN OS 8.

Try this:

# configure
# delete deviceconfig system ssh
# set deviceconfig system ssh ciphers mgmt aes256-ctr
# set deviceconfig system ssh default-hostkey mgmt key-type ECDSA 256
# set deviceconfig system ssh regenerate-hostkeys mgmt key-type ECDSA key-length 256
# set deviceconfig system ssh session-rekey mgmt interval 3600
# set deviceconfig system ssh mac mgmt hmac-sha2-256
# commit
# exit
> set ssh service-restart mgmt

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!