The JMX RMI service in VMware vCenter Server 5.0 before u3e, 5.1 before u3b, 5.5 before u3, and 6.0 before u1 does not restrict registration of MBeans, which allows remote malicious users to execute arbitrary code via the RMI protocol.
Vulnerable Product | Search on Vulmon | Subscribe to Product |
---|---|---|
vmware vcenter server 5.5 |
||
vmware vcenter server 6.0 |
||
vmware vcenter server 5.0 |
||
vmware vcenter server 5.1 |
First patch didn't patch so isn't a patch on the new patch
There's egg on face down VMware way after the company 'fessed up that a patch it delivered last year didn't completely work. The problem the patch failed to patch is VMSA-2015-0007, a nasty that means vCenter Server possesses a remotely accessible JMX RMI service that is not securely configured. News of that problem emerged, along with a patch, on October 1st 2015 to address CVE-2015-2342. So far, so good … until last Friday, February 12th 2016, when VMware updated its original advisory with n...