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-5534: Impact of CVE-2015-5600 on Centrify-Openssh

Authentication Service ,  

12 April,16 at 11:48 AM

Applies to: Centrify-Openssh 6.7p1-5.2.3 or below on all platforms.

Question:
Is Centrify-Openssh impacted by CVE-2015-5600 involving "MaxAuthTries" limit is bypassed and increased the efficiency of the brute-force attack?  If so has this vulnerability been addressed?

Answer:
For information about CVE-2015-5600, please refer to:
  
https://access.redhat.com/security/cve/CVE-2015-5600
https://packetstormsecurity.com/files/132740/OpenSSH-Two-Minute-Cracking-Window.html
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:16.openssh.asc
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5600

This is a Openssh bug that affects local users ONLY, Active Directory users are protected by the account lockout policy. AD users account will be locked after the number of invalid login attempts reaches the lockout threshold value.

In order to protect the local users, account lockout can also be implemented by the following methods:

Solaris:
https://blogs.oracle.com/gbrunett/entry/solaris_10_account_lockout_three
Linux: (Using pam_tally2)
http://wiki.centos.org/HowTos/OS_Protection
http://websistent.com/linux-password-lockout-policy/
AIX:
http://www-01.ibm.com/support/docview.wss?uid=isg3T1020193

OpenSSH 7.0 which addressed CVE-2015-5600 was released on August 12th,2015.​

A new updated version of the Centrify compiled version of OpenSSH will be released in Centrify Suite 2016.

(All external links are provided as a courtesy)

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

Related Articles

 articleKB-6731: Impact of Badlock (CVE-2016-0128/CVE-2016-2118) on Centrify-Enabled Samba articleKB-9455: Fail to upgrade centrify-openssh from Suite2016.1 to Suite2017.2 via native command articleKB-8732: What is the Impact of Disabling SMBv1 (WannaCry) articleKB-6026: Impact of implementing KRBTGT account password reset articleKB-2119: The impact of winbindd on Centrify Enabled Samba articleKB-5141: Impact of CVE-2015-0240 on Centrify-Enabled Samba articleKB-9060: Impact of SMBLoris (ETR-2017-V005) on Centrify Adbindproxy and Samba articleKB-4803: What is the impact of placing files before centrifyda in /etc/nsswitch.conf articleKB-10288: Deprecation of TLS 1.0