# CVE-2024-29855: Hardcoded credentials in Recovery Orchestrator

> Attackers can bypass authentication in Veeam Recovery Orchestrator using a hard-coded JWT secret, potentially taking over accounts.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-vfmf-3vr6-j85g

## What is CVE-2024-29855?

CVE-2024-29855 is a critical vulnerability in Veeam Recovery Orchestrator, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Veeam Recovery Orchestrator.

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

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

## Is CVE-2024-29855 being exploited?

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

Public exploit code:

- PoC for the Veeam Recovery Orchestrator Authentication CVE-2024-29855 (github_poc): https://github.com/sinsinology/CVE-2024-29855

## Other vulnerabilities in Veeam Recovery Orchestrator

- [CVE-2024-22022](https://insights.sbomify.com/CVE-2024-22022/): Information disclosure in Availability Orchestrator (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29855 is a critical vulnerability in Veeam Recovery Orchestrator, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29855 in the wild and no public exploit code.

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

## Sources

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

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