# CVE-2024-22248: Open redirect in VMware SD-WAN Orchestrator

> Attackers can redirect victims to malicious domains via improper path handling, potentially leading to sensitive information disclosure.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Apr 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-x5w9-633f-fvmj

## What is CVE-2024-22248?

CVE-2024-22248 is a high-severity vulnerability in VMware SD-WAN Orchestrator, published on 2 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

VMware SD-WAN Orchestrator contains an open redirect vulnerability.

A malicious actor may be able to redirect a victim to an attacker 
controlled domain due to improper path handling leading to sensitive 
information disclosure.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2024-22248?


## How do I fix CVE-2024-22248?

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

## Is CVE-2024-22248 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22248 and fix it if it is affected.

What it is: CVE-2024-22248 is a high-severity vulnerability in VMware SD-WAN Orchestrator, published on 2 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22248 in the wild and no public exploit code.

Affected product: VMware SD-WAN Orchestrator. 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-2024-22248/ (Markdown: https://insights.sbomify.com/CVE-2024-22248/index.md)
```

## Sources

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

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