# CVE-2021-3723: Command injection in IBM System x 3550 M3

> Authenticated attackers can execute arbitrary OS commands via SSH or Telnet on legacy IBM System x servers.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p94r-3r37-vm3p

## What is CVE-2021-3723?

CVE-2021-3723 is a high-severity command injection vulnerability in IBM System x 3550 M3, published on 12 Nov 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A command injection vulnerability was reported in the Integrated Management Module (IMM) of legacy IBM System x 3550 M3 and IBM System x 3650 M3 servers that could allow the execution of operating system commands over an authenticated SSH or Telnet session.

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

## Which versions are affected by CVE-2021-3723?

It affects 2 products.


Products: Ibm System X3550 M3 Firmware, Ibm System X3650 M3 Firmware.

## How do I fix CVE-2021-3723?

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

## Is CVE-2021-3723 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3723 and fix it if it is affected.

What it is: CVE-2021-3723 is a high-severity command injection vulnerability in IBM System x 3550 M3, published on 12 Nov 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3723 in the wild and no public exploit code.

Affected product: IBM System x 3550 M3. 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-2021-3723/ (Markdown: https://insights.sbomify.com/CVE-2021-3723/index.md)
```

## Sources

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

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