# CVE-2024-29212: Deserialization in Service Provider Console

> Attackers can achieve remote code execution on Veeam Service Provider Console servers via unsafe deserialization in agent communications.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 13 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5h2f-vwh5-pc3g

## What is CVE-2024-29212?

CVE-2024-29212 is a critical unsafe deserialization vulnerability in Veeam Service Provider Console, published on 13 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to an  unsafe de-serialization method used by the Veeam Service Provider Console(VSPC) server in communication between the management agent and its components, under certain conditions, it is possible to perform Remote Code Execution (RCE) on the VSPC server machine.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Veeam Veeam Service Provider Console.

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

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

## Is CVE-2024-29212 being exploited?

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

## Other vulnerabilities in Veeam Service Provider Console

- [CVE-2024-45206](https://insights.sbomify.com/CVE-2024-45206/): Server-side request forgery in Service Provider Console (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29212 is a critical unsafe deserialization vulnerability in Veeam Service Provider Console, published on 13 May 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-29212 in the wild and no public exploit code.

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

## Sources

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

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