# CVE-2022-31794: Command injection in n/a

> Attackers can execute arbitrary commands on Fujitsu ETERNUS CentricStor devices by injecting malicious characters into the unitName parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xr87-5r29-58hr

## What is CVE-2022-31794?

CVE-2022-31794 is a critical command injection vulnerability in n/a, published on 20 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Fujitsu ETERNUS CentricStor CS8000 (Control Center) devices before 8.1A SP02 P04. The vulnerability resides in the requestTempFile function in hw_view.php. An attacker is able to influence the unitName POST parameter and inject special characters such as semicolons, backticks, or command-substitution sequences in order to force the application to execute arbitrary commands.

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

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

It affects 1 product.


Products: Fujitsu Eternus Cs8000 Firmware.

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

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

## Is CVE-2022-31794 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31795](https://insights.sbomify.com/CVE-2022-31795/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31794 is a critical command injection vulnerability in n/a, published on 20 Jun 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-31794 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-2022-31794/ (Markdown: https://insights.sbomify.com/CVE-2022-31794/index.md)
```

## Sources

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

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