# CVE-2020-11953: Command injection in n/a

> Attackers can execute arbitrary code on Rittal PDU and CMC devices due to a command injection vulnerability.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-59fx-725p-7v33

## What is CVE-2020-11953?

CVE-2020-11953 is a high-severity command injection vulnerability in n/a, published on 14 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Rittal PDU-3C002DEC through 5.15.40 and CMCIII-PU-9333E0FB through 3.15.70_4 devices. Attackers can execute code.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2020-11953?

It affects 5 products.


Products: Rittal Cmc Iii Pu 7030.000 Firmware, Rittal Cmciii-Pu-9333e0fb Firmware, Rittal Iot Interface 3124.300, Rittal Lcp-Cw Firmware, Rittal Pdu-3c002dec Firmware.

## How do I fix CVE-2020-11953?

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

## Is CVE-2020-11953 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11951](https://insights.sbomify.com/CVE-2020-11951/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-11956](https://insights.sbomify.com/CVE-2020-11956/): Privilege escalation in n/a (critical 9.8)
- [CVE-2020-11955](https://insights.sbomify.com/CVE-2020-11955/): Misconfiguration in n/a (high 8.8)
- [CVE-2020-11952](https://insights.sbomify.com/CVE-2020-11952/): Auth bypass in n/a (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11953 and fix it if it is affected.

What it is: CVE-2020-11953 is a high-severity command injection vulnerability in n/a, published on 14 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11953 in the wild and no public exploit code.

Affected product: n/a. 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-2020-11953/ (Markdown: https://insights.sbomify.com/CVE-2020-11953/index.md)
```

## Sources

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

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