# CVE-2019-5533: Missing authorization in SD-WAN by VeloCloud

> Enterprise users can improperly access Managed Service Provider account details due to flawed authorization checks in the SD-WAN Orchestrator.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j338-j4px-hxp4

## What is CVE-2019-5533?

CVE-2019-5533 is a medium-severity missing authorization vulnerability in VMware SD-WAN by VeloCloud, published on 28 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2019-5533?

It affects 1 product.


Products: Vmware Sd-Wan by Velocloud.

## How do I fix CVE-2019-5533?

No fix has been published for CVE-2019-5533 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5533 being exploited?

There is no known exploitation of CVE-2019-5533 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5533 and fix it if it is affected.

What it is: CVE-2019-5533 is a medium-severity missing authorization vulnerability in VMware SD-WAN by VeloCloud, published on 28 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5533 in the wild and no public exploit code.

Affected product: VMware SD-WAN by VeloCloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-5533/ (Markdown: https://insights.sbomify.com/CVE-2019-5533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5533
- OSV: https://osv.dev/vulnerability/CVE-2019-5533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-5533/
Summaries are generated and may contain mistakes; the official description above is the record.