# CVE-2022-29875: Deserialization in Biograph Horizon PET/CT Systems

> Unauthenticated attackers can execute arbitrary code on Siemens medical imaging systems via unsafe deserialization if specific TCP ports are reachable.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 1 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qq72-778q-mwmx

## What is CVE-2022-29875?

CVE-2022-29875 is a critical unsafe deserialization vulnerability in Siemens Biograph Horizon PET/CT Systems, published on 1 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in Biograph Horizon PET/CT Systems (All VJ30 versions < VJ30C-UD01), MAGNETOM Family (NUMARIS X: VA12M, VA12S, VA10B, VA20A, VA30A, VA31A), MAMMOMAT Revelation (All VC20 versions < VC20D), NAEOTOM Alpha (All VA40 versions < VA40 SP2), SOMATOM X.cite (All versions < VA30 SP5 or VA40 SP2), SOMATOM X.creed (All versions < VA30 SP5 or VA40 SP2), SOMATOM go.All (All versions < VA30 SP5 or VA40 SP2), SOMATOM go.Now (All versions < VA30 SP5 or VA40 SP2), SOMATOM go.Open Pro (All versions < VA30 SP5 or VA40 SP2), SOMATOM go.Sim (All versions < VA30 SP5 or VA40 SP2), SOMATOM go.Top (All versions < VA30 SP5 or VA40 SP2), SOMATOM go.Up (All versions < VA30 SP5 or VA40 SP2), Symbia E/S (All VB22 versions < VB22A-UD03), Symbia Evo (All VB22 versions < VB22A-UD03), Symbia Intevo (All VB22 versions < VB22A-UD03), Symbia T (All VB22 versions < VB22A-UD03), Symbia.net (All VB22 versions < VB22A-UD03), syngo.via VB10 (All versions), syngo.via VB20 (All versions), syngo.via VB30 (All versions), syngo.via VB40 (All versions < VB40B HF06), syngo.via VB50 (All versions), syngo.via VB60 (All versions < VB60B HF02). The application deserialises untrusted data without sufficient validations that could result in an arbitrary deserialization. This could allow an unauthenticated attacker to execute code in the affected system if ports 32912/tcp or 32914/tcp are reachable.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2022-29875?

It affects 18 products.


Products: Siemens Biograph Horizon Pet\/Ct Systems Firmware, Siemens Magnetom Numaris X Firmware, Siemens Mammomat Revelation Firmware, Siemens Naeotom Alpha Firmware, Siemens Somatom Go.all Firmware, Siemens Somatom Go.now Firmware, Siemens Somatom Go.open Pro Firmware, Siemens Somatom Go.sim Firmware, Siemens Somatom Go.up Firmware, Siemens Somatom X.cite Firmware, Siemens Somatom X.creed Firmware, Siemens Symbia.net, Siemens Symbia E Firmware, Siemens Symbia Evo Firmware, Siemens Symbia Intevo Firmware, Siemens Symbia S Firmware, Siemens Symbia T Firmware, Siemens Syngo.via.

## How do I fix CVE-2022-29875?

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

## Is CVE-2022-29875 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29875 and fix it if it is affected.

What it is: CVE-2022-29875 is a critical unsafe deserialization vulnerability in Siemens Biograph Horizon PET/CT Systems, published on 1 Jun 2022. 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-2022-29875 in the wild and no public exploit code.

Affected product: Siemens Biograph Horizon PET/CT Systems. 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-2022-29875/ (Markdown: https://insights.sbomify.com/CVE-2022-29875/index.md)
```

## Sources

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

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