CyberSecBulletin
CVE-2022-29875NVD status: Modified

Biograph Horizon PET/CT Systems: Deserialization of Untrusted Data

Published Updated By the CyberSecBulletin desk

CVE-2022-29875 is a critical-severity deserialization of untrusted data vulnerability in Biograph Horizon PET/CT Systems from Siemens, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Biograph Horizon PET/CT Systems versions: All VJ30 versions < VJ30C-UD01. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.87% chance of exploitation within 30 days, higher than 80% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Biograph Horizon Pet/ct Systems Firmware to vj30c-ud01 or a later version.
  2. Update Mammomat Revelation Firmware to vc20d or a later version.
  3. Update Somatom X.cite Firmware to va30 or a later version.
  4. Read the advisory on siemens-healthineers.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
SiemensBiograph Horizon PET/CT SystemsAll VJ30 versions < VJ30C-UD01Not stated
SiemensMAGNETOM FamilyNUMARIS X: VA12M, VA12S, VA10B, VA20A, VA30A, VA31ANot stated
SiemensMAMMOMAT RevelationAll VC20 versions < VC20DNot stated
SiemensNAEOTOM AlphaAll VA40 versions < VA40 SP2Not stated
SiemensSOMATOM X.citeAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM X.creedAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM go.AllAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM go.NowAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM go.Open ProAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM go.SimAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM go.TopAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSOMATOM go.UpAll versions < VA30 SP5 or VA40 SP2Not stated
SiemensSymbia E/SAll VB22 versions < VB22A-UD03Not stated
SiemensSymbia EvoAll VB22 versions < VB22A-UD03Not stated
SiemensSymbia IntevoAll VB22 versions < VB22A-UD03Not stated
SiemensSymbia TAll VB22 versions < VB22A-UD03Not stated
SiemensSymbia.netAll VB22 versions < VB22A-UD03Not stated
Siemenssyngo.via VB10All versionsNot stated
Siemenssyngo.via VB20All versionsNot stated
Siemenssyngo.via VB30All versionsNot stated
Siemenssyngo.via VB40All versions < VB40B HF06Not stated
Siemenssyngo.via VB50All versionsNot stated
Siemenssyngo.via VB60All versions < VB60B HF02Not stated
SiemensBiograph Horizon Pet/ct Systems Firmwarevj30 up to, but not including, vj30c-ud01vj30c-ud01
SiemensMagnetom Numaris X Firmwareva10b; va12m; va12s; va20a; va30a; va31aNot stated

Version data comes from the organisation that assigned the CVE; 15 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalNVD
CVSS 2.09.3HighNVD

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How developers prevent this class of flaw

  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Explicitly define a final object() to prevent deserialization.

More Deserialization of Untrusted Data vulnerabilities (CWE-502)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Deserialization of Untrusted Data vulnerabilities

Spotted an error? Tell us.