CVE-2013-1405
First published: Fri Feb 15 2013(Updated: )
VMware vCenter Server 4.0 before Update 4b and 4.1 before Update 3a, VMware VirtualCenter 2.5, VMware vSphere Client 4.0 before Update 4b and 4.1 before Update 3a, VMware VI-Client 2.5, VMware ESXi 3.5 through 4.1, and VMware ESX 3.5 through 4.1 do not properly implement the management authentication protocol, which allow remote servers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| VMware vCenter | =4.0-update_4 | |
| VMware vCenter | =4.1-update_3 | |
| VMware vCenter | =2.5 | |
| VMware vSphere Client | =4.0-update_4 | |
| VMware vSphere Client | =4.1-update_3 | |
| VMware vSphere Client | =2.5 | |
| VMware ESXi | =3.5 | |
| VMware ESXi | =3.5-1 | |
| VMware ESXi | =4.0 | |
| VMware ESXi | =4.0-1 | |
| VMware ESXi | =4.0-2 | |
| VMware ESXi | =4.0-3 | |
| VMware ESXi | =4.0-4 | |
| VMware ESXi | =4.1 | |
| VMware ESXi | =3.5 | |
| VMware ESXi | =3.5-update1 | |
| VMware ESXi | =3.5-update2 | |
| VMware ESXi | =3.5-update3 | |
| VMware ESXi | =4.0 | |
| VMware ESXi | =4.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2013-1405?
The severity of CVE-2013-1405 is classified as critical due to improper authentication in VMware products.
How do I fix CVE-2013-1405?
To fix CVE-2013-1405, upgrade to the latest patched versions of VMware vCenter Server, vSphere Client, and ESXi/ESX as specified in VMware's security advisory.
Which VMware products are affected by CVE-2013-1405?
CVE-2013-1405 affects VMware vCenter Server 4.0 before Update 4b, 4.1 before Update 3a, VMware VirtualCenter 2.5, VMware vSphere Client 4.0 before Update 4b, and various versions of ESXi and ESX.
What potential risks are associated with CVE-2013-1405?
The risks associated with CVE-2013-1405 include unauthorized access to restricted areas of the management interface, leading to potential data breaches or system compromises.
Is there a workaround for CVE-2013-1405?
No official workaround is recommended for CVE-2013-1405; users should apply the security updates to remediate the vulnerability.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/references
- agent/author
- agent/weakness
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/vmware
- canonical/vmware vcenter
- version/vmware vcenter/4.0-update_4
- version/vmware vcenter/4.1-update_3
- version/vmware vcenter/2.5
- canonical/vmware vsphere client
- version/vmware vsphere client/4.0-update_4
- version/vmware vsphere client/4.1-update_3
- version/vmware vsphere client/2.5
- canonical/vmware esxi
- version/vmware esxi/3.5
- version/vmware esxi/3.5-1
- version/vmware esxi/4.0
- version/vmware esxi/4.0-1
- version/vmware esxi/4.0-2
- version/vmware esxi/4.0-3
- version/vmware esxi/4.0-4
- version/vmware esxi/4.1
- version/vmware esxi/3.5-update1
- version/vmware esxi/3.5-update2
- version/vmware esxi/3.5-update3