{"id":41129,"date":"2021-05-26T02:04:18","date_gmt":"2021-05-26T02:04:18","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/vmware-reveals-critical-vcenter-hole-it-says-needs-to-be-considered-at-once\/"},"modified":"2021-05-26T02:04:18","modified_gmt":"2021-05-26T02:04:18","slug":"vmware-reveals-critical-vcenter-hole-it-says-needs-to-be-considered-at-once","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/vmware-reveals-critical-vcenter-hole-it-says-needs-to-be-considered-at-once\/","title":{"rendered":"VMware reveals critical vCenter hole it says \u2018needs to be considered at once\u2019"},"content":{"rendered":"

VMware has revealed a critical bug that can be exploited to achieve unauthenticated remote code execution in the very core of a virtualised system \u2013 vCenter Server.<\/p>\n

The culprit is the vSphere HTML5 client, which by default includes the Virtual SAN Health plugin \u2013 even if you don\u2019t run a VMware VSAN. That plugin lacks input validation and the result, as explained by VMware\u2019s advisory<\/a> this week, is: \u201cA malicious actor with network access to port 443 may exploit this issue to execute commands with unrestricted privileges on the underlying operating system that hosts vCenter Server.\u201d<\/p>\n

As vCenter is the tool with which VMware users drive their fleets of virtual machines, the bug is rated a 9.8 out of 10 in severity.<\/p>\n