Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-11511: Nessus security scanner showing libssh vulnerability in Centrify Connectors

Privileged Access Service ,  

26 January,19 at 03:44 AM

Problem: Nessus security scanner reports a libssh vulnerability in Centrify Connectors

Cause: The Centrify connector uses /n Software's SSH server library.  This library, while similar to libssh, does not contain the libssh that is reported by the Nessus security scan report.  However, during the scan, a different vulnerability, that caused a channel to be opened for a short window when it should not have been open, was discovered.

Resolution: That issue was subsequently fixed by /n Software.   The library with the fix, /n Software version 16.0.6883.0,  is built into Centrify Privileged Access Service 18.11 connectors.  Installing the 18.11 Centrify connector will resolve the Nessus security scan report.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-11471: How to configure network encryption types Ciphers on CPS on-prem Connectors articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-11225: Do CVE-2018-10933 vulnerabilities affect Centrify DirectControl? articleKB-6041: How to show current license type in use by adclient articleKB-4257: Troubleshooting Integrated Windows Authentication (IWA) with Centrify Identity Service articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0)