VMware

VMware changes default Active Directory Integration settings CVE-2024-37085, CVE-2024-37086, CVE-2024-37087

Learn about new guidance vulnerabilities in VMware Active Directory integration regarding CVE-2024-37085, CVE-2024-37086, CVE-2024-37087

There has been a lot of back and forth on Active Directory integration security with VMware lately and a really great article by Bob Plankers on Active Directory integration and IdP in general. You can read that here, definitely a good one: Thoughts on CVE-2024-37085 and ESXi (plankers.com).

Why are settings being changed?

In the VMSA for the specific CVE of VMware ESXi Active Directory Integration Authentication Bypass (CVE-2024-37085) and the linked KB article, it was noted that several ESXi advanced settings had default values that are not secure by default. As an example, the ESX Admins is automatically given a role when an ESXi host is joined by the VI Admin to the Active Directory Domain. That role is the VIM Admin.

VMware also makes this note regarding the ESX Admins group:

Note: The ESX Admins group will be added to the host with Admin privileges once the host is added to Active Directory. It is recommended to change these settings before joining the domain. These settings take effect within a minute. A reboot is not required.

What is changing?

There are just a few advanced settings that are changing in regards to what VMware is now recommending for settings on your ESXi hosts. They are now recommending the following advanced settings changes:

Config.HostAgent.plugins.hostsvc.esxAdminsGroupAutoAdd from true to false
Config.HostAgent.plugins.vimsvc.authValidateInterval from 1440 to 90
Config.HostAgent.plugins.hostsvc.esxAdminsGroup from "ESX Admins" to "" 
Checking the config.hostagent.plugins.hostsvc.esxadminsgroupautoadd parameter
Checking the config.hostagent.plugins.hostsvc.esxadminsgroupautoadd parameter
Changing the config.hostagent.plugins.vimsvc.authvalidateinterval advanced setting
Changing the config.hostagent.plugins.vimsvc.authvalidateinterval advanced setting
Changing the config.hostagent.plugins.hostsvc.esxadminsgroup advanced parameter
Changing the config.hostagent.plugins.hostsvc.esxadminsgroup advanced parameter

Also, if you have already joined ESXi hosts to Active Directory before the workaround is put in place, the new direction is to remove the Admin permissions for the AD group ESX Admins. There is a command you can run to do this:

esxcli system permission unset -i 'DOMAIN\esx^admins' --group

To make sure of what permissions are set for VIM permissions you can use the command:

esxcli system permission list
Checking vim permissions on esxi host
Checking vim permissions on esxi host

Below is VMware’s response Matrix for the VMware ESXi Active Directory Integration Authentication Bypass (CVE-2024-37085) for those that would like to look at the following table:

VMware ProductVersionRunning OnCVECVSSv3SeverityFixed VersionWorkaroundsAdditional Documentation
ESXi 8.0AnyCVE-2024-370856.8ModerateESXi80U3-24022510KB369707None
ESXi 7.0AnyCVE-2024-370856.8ModerateNo Patch PlannedKB369707None
VMware Cloud Foundation5.xAnyCVE-2024-370856.8Moderate5.2KB369707None
VMware Cloud Foundation4.xAnyCVE-2024-370856.8ModerateNo Patch PlannedKB369707None

The response matrix for the VMware ESXi out-of-bounds read vulnerability (CVE-2024-37086):

VMware ProductVersionRunning OnCVECVSSv3SeverityFixed VersionWorkaroundsAdditional Documentation
ESXi 8.0AnyCVE-2024-370866.8ModerateESXi80U3-24022510NoneNone
ESXi 7.0AnyCVE-2024-370866.8ModerateESXi70U3sq-23794019NoneNone
VMware Cloud Foundation5.xAnyCVE-2024-370866.8Moderate5.2NoneNone
VMware Cloud Foundation4.xAnyCVE-2024-370866.8ModerateAsync patch to ESXi 7.0 U3qNoneAsync Patching Guide: KB88287

The response matrix for the VMware vCenter denial-of-service vulnerability (CVE-2024-37087):

VMware ProductVersionRunning OnCVECVSSv3SeverityFixed VersionWorkaroundsAdditional Documentation
vCenter Server 8.0AnyCVE-2024-370875.3Moderate8.0 U3NoneNone
vCenter Server  7.0AnyCVE-2024-370875.3Moderate7.0 U3q [1]NoneNone
VMware Cloud Foundation5.xAnyCVE-2024-370875.3Moderate5.2NoneNone
VMware Cloud Foundation4.xAnyCVE-2024-370875.3ModerateAsync patch to 7.0 U3q [1]NoneAsync Patching Guide: KB88287

Wrapping up

If you read the latest VMware Security best practices, VMware no longer recommends joining your ESXi hosts to an Active Directory Domain Services environment. There are just too many risks to doing this. A lot of the ransomware gangs are compromising vCenter Server using domain credentials. Not joining your vSphere environment to Active Directory just helps to eliminate this as a risk to the environment.

Subscribe to VirtualizationHowto via Email 🔔

Enter your email address to subscribe to this blog and receive notifications of new posts by email.



Brandon Lee

Brandon Lee is the Senior Writer, Engineer and owner at Virtualizationhowto.com, and a 7-time VMware vExpert, with over two decades of experience in Information Technology. Having worked for numerous Fortune 500 companies as well as in various industries, He has extensive experience in various IT segments and is a strong advocate for open source technologies. Brandon holds many industry certifications, loves the outdoors and spending time with family. Also, he goes through the effort of testing and troubleshooting issues, so you don't have to.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.