dbcve.org
Biograph Horizon Pet\/ct Systems FirmwareOperating system · Siemens

CVE-2022-29875

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Siemens medical imaging systems contain an insecure deserialization vulnerability where the application deserializes untrusted data without sufficient validation. This improper deserialization can be exploited by sending malicious serialized objects to ports 32912/tcp or 32914/tcp, allowing unauthenticated remote code execution.

MitigationApply vendor-supplied patches (specific version updates listed in the CVE) and restrict network access to ports 32912/tcp and 32914/tcp using firewalls or network segmentation to prevent unauthenticated attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Biograph Horizon Pet\/ct Systems FirmwareOperating system
Affected:>= vj30, < vj30c-ud01
Magnetom Numaris X FirmwareOperating system
Affected:= va10b= va12m= va12s= va20a= va30a= va31a
Mammomat Revelation FirmwareOperating system
Affected:>= vc20, < vc20d
Naeotom Alpha FirmwareOperating system
Affected:= va40
Somatom X.cite FirmwareOperating system
Affected:< va30= va30= va40
Somatom X.creed FirmwareOperating system
Affected:< va30= va30= va40
Somatom Go.all FirmwareOperating system
Affected:< va30= va30= va40
Somatom Go.now FirmwareOperating system
Affected:< va30= va30= va40

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the medical imaging device model
    Locate the Siemens medical imaging system in your environment and note the product name (e.g., Biograph Horizon, Magnetom Numaris X, Mammomat Revelation, Naeotom Alpha, Somatom X.cite, Somatom X.creed, Somatom Go.all, or Somatom Go.now). This information is typically found on the device label, in the system documentation, or via the device's built-in service interface.
    Affected if The device is any of the Siemens models listed in the CVE (Biograph Horizon, Magnetom Numaris X, Mammomat Revelation, Naeotom Alpha, Somatom X.cite, Somatom X.creed, Somatom Go.all, or Somatom Go.now).
  2. Determine the installed firmware version
    Access the device's service or administration interface and retrieve the firmware version. This is usually displayed in the system information, service menu, or can be obtained via Siemens service documentation specific to that device model.
    Affected if The firmware version falls within the affected ranges: Biograph Horizon (>= vj30, < vj30c-ud01), Magnetom Numaris X (va10b, va12m, va12s, va20a, va30a, va31a), Mammomat Revelation (>= vc20, < vc20d), Naeotom Alpha (va40), or any Somatom model (X.cite, X.creed, Go.all, Go.now) with version < va30, =
  3. Verify if network ports 32912/tcp or 32914/tcp are accessible
    Scan the device or network segment for open ports 32912/tcp and 32914/tcp using a network scanner (e.g., nmap -p 32912,32914 <device_ip>). Check firewall rules and network segmentation configurations to determine if these ports are exposed to untrusted networks.
    Affected if Ports 32912/tcp or 32914/tcp are open and accessible from network segments that are not trusted or are externally exposed.

The environment is affected if it contains a Siemens medical imaging device from the listed product line with a firmware version matching the affected ranges AND ports 32912/tcp or 32914/tcp are accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches (specific version updates listed in the CVE) and restrict network access to ports 32912/tcp and 32914/tcp using firewalls or network segmentation to prevent unauthenticated attacks.

Recommended fix High confidence

Firmware version specific to each product: VJ30C-UD01 for Biograph Horizon; VA30A/VA31A for NUMARIS X; VC20D for MAMMOMAT Revelation; VA40 SP2 for NAEOTOM Alpha; VA30 SP5 or VA40 SP2 for SOMATOM X.cite/X.creed/go.All/go.Now/go series; VB40B HF06 for syngo.via VB40; VB60B HF02 for syngo.via VB60; VB2

  1. 1. Identify the exact model and current firmware version of the affected Siemens Healthineers system using the system console or service interface
  2. 2. For Biograph Horizon PET/CT systems: Upgrade to firmware version VJ30C-UD01 or later
  3. 3. For MAGNETOM NUMARIS X systems: Upgrade to VA30A or VA31A (which are not vulnerable)
  4. 4. For MAMMOMAT Revelation: Upgrade to firmware version VC20D or later
  5. 5. For NAEOTOM Alpha: Upgrade to VA40 SP2 or later
  6. 6. For SOMATOM X.cite: Upgrade to VA30 SP5 or VA40 SP2 or later
  7. 7. For SOMATOM X.creed: Upgrade to VA30 SP5 or VA40 SP2 or later
  8. 8. For SOMATOM go.All, go.Now, go.Open Pro, go.Sim, go.Top, go.Up: Upgrade to VA30 SP5 or VA40 SP2 or later
Caveat Medical device firmware upgrades require validation and may need vendor support; ensure compatibility with dependent systems and clinical workflows before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Biograph Horizon Pet\/ct Systems Firmware Scoped from the published advisory
  • Consultation40.0 h
  • Implementation80.0 h
  • Testing60.0 h
  • Review / QA20.0 h
200.0 hours of engineering $35,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $56,000.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29875 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data