Read the docs
TI-2014-00924 Aliases CVE-2014-1210GHSA-7rj8-xh5v-9hqg

VMware vSphere Client 5.0 before Update 3 and 5.1 before Update 2 does not properly…

Priority LOW 27CWE-310Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
— Not recorded in CVSS 2.0
Attack complexity
Medium
Impact type
—
Confidentiality · integrity · availability
Partial · Partial · None
Fix status
No fix listed

Attack profile from CVSS 2.0 · NVD. Fix status from CNA.

Summary

VMware vSphere Client 5.0 before Update 3 and 5.1 before Update 2 does not properly validate X.509 certificates, which allows man-in-the-middle attackers to spoof SSL servers via a crafted certificate.

Why it matters now

EPSS 0.00677 52nd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:vmware:vsphere_client:5.0:*:*:*:*:*:*:*5.0VulnerableVMware
cpe:2.3:a:vmware:vsphere_client:5.1:*:*:*:*:*:*:*5.1VulnerableVMware
  • cpe:2.3:a:vmware:vsphere_client:5.0:*:*:*:*:*:*:* Versions 5.0 Vulnerable ·VMware
  • cpe:2.3:a:vmware:vsphere_client:5.1:*:*:*:*:*:*:* Versions 5.1 Vulnerable ·VMware

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2014-1210
  2. 2026-10-03 Alias added: GHSA-7rj8-xh5v-9hqg

References

Advisory 1

  • TI-2013-01226 VMware vCenter Server 4.0 before Update 4b and 4.1 before Update 3a, VMware VirtualCenter… CVSS 2.0HIGH 10.0
  • TI-2014-00923 VMware vSphere Client 4.0, 4.1, 5.0 before Update 3, and 5.1 before Update 2 does not… CVSS 2.0HIGH 9.3
  • TI-2016-06353 VMware vSphere Client 5.5 before U3e and 6.0 before U2a allows remote vCenter Server and… CVSS 3.0MEDIUM 5.8

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences