CVE-2013-1405: Critical severity vmware vcenter vulnerability

Published 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.

Affected Software

20 affected components
VMware vCenter Server=4.0-update_4
VMware vCenter Server=4.1-update_3
VMware VirtualCenter=2.5
VMware vSphere Client=4.0-update_4
VMware vSphere Client=4.1-update_3
VMware VI-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 ESX=3.5
VMware ESX=3.5-update1
VMware ESX=3.5-update2
VMware ESX=3.5-update3
VMware ESX=4.0
VMware ESX=4.1

Event History

Feb 15, 2013
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203