# CVE-2022-29873: Other in SICAM T

> Unauthenticated attackers can execute arbitrary code or cause denial of service on Siemens SICAM T devices due to improper parameter validation.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2022
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-v36v-c6xp-cpv3

## What is CVE-2022-29873?

CVE-2022-29873 is a critical vulnerability in Siemens SICAM T, published on 10 May 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 SICAM T (All versions < V3.0). Affected devices do not properly validate parameters of certain GET and POST requests. This could allow an unauthenticated 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.

Weakness: CWE-141 (Improper Neutralization of Parameter/Argument Delimiters)

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

It affects 36 products.


Products: Siemens 7kg8500-0aa00-0aa0 Firmware, Siemens 7kg8500-0aa00-2aa0 Firmware, Siemens 7kg8500-0aa10-0aa0 Firmware, Siemens 7kg8500-0aa10-2aa0 Firmware, Siemens 7kg8500-0aa30-0aa0 Firmware, Siemens 7kg8500-0aa30-2aa0 Firmware, Siemens 7kg8501-0aa01-0aa0 Firmware, Siemens 7kg8501-0aa01-2aa0 Firmware, Siemens 7kg8501-0aa02-0aa0 Firmware, Siemens 7kg8501-0aa02-2aa0 Firmware, Siemens 7kg8501-0aa11-0aa0 Firmware, Siemens 7kg8501-0aa11-2aa0 Firmware, Siemens 7kg8501-0aa12-0aa0 Firmware, Siemens 7kg8501-0aa12-2aa0 Firmware, Siemens 7kg8501-0aa31-0aa0 Firmware, Siemens 7kg8501-0aa31-2aa0 Firmware, Siemens 7kg8501-0aa32-0aa0 Firmware, Siemens 7kg8501-0aa32-2aa0 Firmware, Siemens 7kg8550-0aa00-0aa0 Firmware, Siemens 7kg8550-0aa00-2aa0 Firmware and 16 more.

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

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

## Is CVE-2022-29873 being exploited?

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

## Other vulnerabilities in Siemens SICAM T

- [CVE-2022-41665](https://insights.sbomify.com/CVE-2022-41665/): A vulnerability has been identified in SICAM P850 (7KG8500-0AA00-0AA0) (All versions < V3.10), SICAM P850 (7KG8500-0AA00-2AA0) (All versions (critical 9.8)
- [CVE-2022-29874](https://insights.sbomify.com/CVE-2022-29874/): Information disclosure in SICAM T (high 8.8)
- [CVE-2022-29872](https://insights.sbomify.com/CVE-2022-29872/): Other in SICAM T (high 8.7)
- [CVE-2022-40226](https://insights.sbomify.com/CVE-2022-40226/): Auth bypass in SICAM P850 (high 7.5)
- [CVE-2022-29878](https://insights.sbomify.com/CVE-2022-29878/): Auth bypass in SICAM T (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29873 is a critical vulnerability in Siemens SICAM T, published on 10 May 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-29873 in the wild and no public exploit code.

Affected product: Siemens SICAM T. 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-29873/ (Markdown: https://insights.sbomify.com/CVE-2022-29873/index.md)
```

## Sources

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

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