A vulnerability has been identified in SICAM T (All versions < V3.0).

published 2022-05-10 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-34184

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

A vulnerability has been identified in SICAM T (All versions < V3.0). Affected devices do not properly validate parameters of POST requests. This could allow an authenticated attacker to set the device to a denial of service state or to control the program counter and, thus, execute arbitrary code on the device.

Patch / fix

fixed in 1 links 1

Siemens SICAM T V3.0

cert-portal.siemens.com/productcert/pdf/ssa-165073.pdf advisory

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-132-07 updated 2025-05-06 cvss 8.8

Siemens SICAM P850 and SICAM P855

Siemens SICAM P850 <V3.00
affected: fixed in V3.00, mitigation support.industry.siemens.com
Siemens SICAM P855 <V3.00
affected: fixed in V3.00, mitigation support.industry.siemens.com

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA	4.0	8.7	CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA	4.0	8.7	CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

Siemens SICAM T

Classification

Weakness

CWE-141 Improper Neutralization of Parameter/Argument Delimiters
CWE-20 Improper Input Validation

References

Sources

CVE List CVE-2022-29872
NVD CVE-2022-29872

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary