# CVE-2022-36323: Command injection in RUGGEDCOM RM1224 LTE(4G) EU

> An authenticated admin can inject code to spawn a root shell on Siemens RUGGEDCOM and SCALANCE routers.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2022
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-qj75-j4wq-j748

## What is CVE-2022-36323?

CVE-2022-36323 is a critical command injection vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 10 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Affected devices do not properly sanitize an input field.  This could allow an authenticated remote attacker with administrative privileges to inject code or spawn a system root shell.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 90 products.


Products: Siemens Scalance M-800 Firmware, Siemens Scalance S615 Firmware, Siemens Scalance Sc-600 Firmware, Siemens Scalance Sc622-2c Firmware, Siemens Scalance Sc632-2c Firmware, Siemens Scalance Sc636-2c Firmware, Siemens Scalance Sc642-2c Firmware, Siemens Scalance Sc646-2c Firmware, Siemens Scalance W700 Ieee 802.11ac Firmware, Siemens Scalance W700 Ieee 802.11ax Firmware, Siemens Scalance W700 Ieee 802.11n Firmware, Siemens Scalance Xb-200 Firmware, Siemens Scalance Xb205-3 Firmware, Siemens Scalance Xb205-3ld Firmware, Siemens Scalance Xb208 Firmware, Siemens Scalance Xb213-3 Firmware, Siemens Scalance Xb213-3ld Firmware, Siemens Scalance Xb216 Firmware, Siemens Scalance Xc-200 Firmware, Siemens Scalance Xc206-2 Firmware and 70 more.

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

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

## Is CVE-2022-36323 being exploited?

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

## Other vulnerabilities in Siemens RUGGEDCOM RM1224 LTE(4G) EU

- [CVE-2022-36324](https://insights.sbomify.com/CVE-2022-36324/): Denial of service in RUGGEDCOM RM1224 LTE(4G) EU (high 7.5)
- [CVE-2022-36325](https://insights.sbomify.com/CVE-2022-36325/): Cross-site scripting in RUGGEDCOM RM1224 LTE(4G) EU (medium 6.8)
- [CVE-2016-7090](https://insights.sbomify.com/CVE-2016-7090/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36323 is a critical command injection vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 10 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36323 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM RM1224 LTE(4G) EU. 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-36323/ (Markdown: https://insights.sbomify.com/CVE-2022-36323/index.md)
```

## Sources

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

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