VMware has updated vCenter Server to address multiple security vulnerabilities.

Apply the missing patch(es).

vCenter Server AD anonymous LDAP binding credential by-pass vCenter Server when deployed in an environment that uses Active Directory (AD) with anonymous LDAP binding enabled doesn't properly handle login credentials. In this environment, authenticating to vCenter Server with a valid user name and a blank password may be successful even if a non-blank password is required for the account. The issue is present on vCenter Server 5.1, 5.1a and 5.1b if AD anonymous LDAP binding is enabled. The issue is addressed in vCenter Server 5.1 Update 1 by removing the possibility to authenticate using blank passwords. This change in the authentication mechanism is present regardless if anonymous binding is enabled or not. Workaround The workaround is to discontinue the use of AD anonymous LDAP binding if it is enabled in your environment. AD anonymous LDAP binding is not enabled by default. The TechNet article listed in the references section explains how to check for anonymous binding (look for 'anonymous binding' in the article: anonymous binding is enabled if the seventh bit of the dsHeuristics attribute is set to 2) Oracle (Sun) JRE is updated to version 1.6.0_37, which addresses multiple security issues that existed in earlier releases of Oracle (Sun) JRE.

vCenter Server 5.1 without Update 1 vCenter Server 5.0 without Update 3

Check the build number.

• http://www.vmware.com/security/advisories/VMSA-2013-0006.html

---

Updated on 2015-03-25