Quantcast
Channel: VMware Communities: Message List - ESXi
Viewing all articles
Browse latest Browse all 28826

Re: Do we need the SLP Service on Port 427

$
0
0

Hi All,

This is the text of the VMware SR I opened and their response is below:

This is a question about the vulnerability announcement sent today: [Security-announce] VMSA-2019-0022 VMware ESXi and Horizon DaaS updates address OpenSLP remote code execution vulnerability (CVE-2019-5544)

 

Due to constraints in our environment we are not able to update to the recommended build of:

Product:ESXi (Embedded and Installable) 6.7.0 -  ESXi670-201912001 - 12/05/2019 - 15160138

 

Prior to performing the workaround per KB76372 on our ESXi hosts we need to know if any vSphere applications will be affected by applying the workaround to include the vRealize Suite vRA, vCO, vRB, Loginsight, vRNI, vROPS, NSX, etc....

 

VMware response:

. When performing the workaround as described in https://kb.vmware.com/s/article/76372 we will lose access to hardware health monitoring at the vCenter level. However none of the other vSphere products you mentioned should be affected by performing this workaround.

 

 

In a second question I asked if Proactive HA would be affected. They said no.

 

It does not appear that ESXi or any apps use port 427 with the exception of Hardware Health. So if you're relying on hardware health you may have an issue.

I am waiting for a response to see if this wil affect Hardware Alerts like ‘host memory’, Host processor’, host hardware voltage’ etc….

 

Update from VMware support:

. In this case yes by disabling SLP and port 427 we will limit if not remove the ability to receive alerts for hardware health from the vCenter level.

If you have out of band management solutions like iDRAC, ILO, UCS, etc then you should still have some access to hardware health monitoring.



Viewing all articles
Browse latest Browse all 28826

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>