# CVE-2024-22021: Missing authorization in Availability Orchestrator

> Low-privileged users can access recovery plans from unauthorized scopes due to missing authorization checks in Veeam Recovery Orchestrator.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 7 Feb 2024
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-3jx4-3grj-xm5w

## What is CVE-2024-22021?

CVE-2024-22021 is a medium-severity missing authorization vulnerability in Veeam Availability Orchestrator, published on 7 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability CVE-2024-22021 allows a Veeam Recovery Orchestrator user with a low privileged role (Plan Author) to retrieve plans from a Scope other than the one they are assigned to.

Weakness: CWE-285 (Improper Authorization)

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

It affects 3 products.


Products: Veeam Availability Orchestrator, Veeam Disaster Recovery Orchestrator, Veeam Recovery Orchestrator.

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

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

## Is CVE-2024-22021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22021 is a medium-severity missing authorization vulnerability in Veeam Availability Orchestrator, published on 7 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22021 in the wild and no public exploit code.

Affected product: Veeam Availability 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-22021/ (Markdown: https://insights.sbomify.com/CVE-2024-22021/index.md)
```

## Sources

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

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