# CVE-2023-36751: Command injection in RUGGEDCOM ROX MX5000

> Authenticated privileged attackers can execute arbitrary code with root privileges via command injection in the web interface install-app parameter.

- **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:** 11 Jul 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-m988-f2xj-5386

## What is CVE-2023-36751?

CVE-2023-36751 is a critical command injection vulnerability in Siemens RUGGEDCOM ROX MX5000, published on 11 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0), RUGGEDCOM ROX RX1400 (All versions < V2.16.0), RUGGEDCOM ROX RX1500 (All versions < V2.16.0), RUGGEDCOM ROX RX1501 (All versions < V2.16.0), RUGGEDCOM ROX RX1510 (All versions < V2.16.0), RUGGEDCOM ROX RX1511 (All versions < V2.16.0), RUGGEDCOM ROX RX1512 (All versions < V2.16.0), RUGGEDCOM ROX RX1524 (All versions < V2.16.0), RUGGEDCOM ROX RX1536 (All versions < V2.16.0), RUGGEDCOM ROX RX5000 (All versions < V2.16.0). The install-app URL parameter in the web interface of affected devices is vulnerable to command injection due to missing server side input sanitation. This could allow an authenticated privileged remote attacker to execute arbitrary code with root privileges.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2023-36751?

It affects 11 products.


Products: Siemens Ruggedcom Rox Mx5000 Firmware, Siemens Ruggedcom Rox Mx5000re Firmware, Siemens Ruggedcom Rox Rx1400 Firmware, Siemens Ruggedcom Rox Rx1500 Firmware, Siemens Ruggedcom Rox Rx1501 Firmware, Siemens Ruggedcom Rox Rx1510 Firmware, Siemens Ruggedcom Rox Rx1511 Firmware, Siemens Ruggedcom Rox Rx1512 Firmware, Siemens Ruggedcom Rox Rx1524 Firmware, Siemens Ruggedcom Rox Rx1536 Firmware, Siemens Ruggedcom Rox Rx5000 Firmware.

## How do I fix CVE-2023-36751?

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

## Is CVE-2023-36751 being exploited?

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

## Other vulnerabilities in Siemens RUGGEDCOM ROX MX5000

- [CVE-2023-36750](https://insights.sbomify.com/CVE-2023-36750/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36752](https://insights.sbomify.com/CVE-2023-36752/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36753](https://insights.sbomify.com/CVE-2023-36753/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36754](https://insights.sbomify.com/CVE-2023-36754/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)
- [CVE-2023-36755](https://insights.sbomify.com/CVE-2023-36755/): Command injection in RUGGEDCOM ROX MX5000 (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36751 and fix it if it is affected.

What it is: CVE-2023-36751 is a critical command injection vulnerability in Siemens RUGGEDCOM ROX MX5000, published on 11 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36751 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM ROX MX5000. 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-2023-36751/ (Markdown: https://insights.sbomify.com/CVE-2023-36751/index.md)
```

## Sources

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

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