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

> An authenticated attacker can execute arbitrary shell commands on Hirschmann BAT-C2 devices via unsanitized input in the FsCreateDir function.

- **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:** 25 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-355f-6hm6-3cc4

## What is CVE-2022-40282?

CVE-2022-40282 is a high-severity command injection vulnerability in n/a, published on 25 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web server of Hirschmann BAT-C2 before 09.13.01.00R04 allows authenticated command injection. This allows an authenticated attacker to pass commands to the shell of the system because the dir parameter of the FsCreateDir Ajax function is not sufficiently sanitized. The vendor's ID is BSECV-2022-21.

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

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

It affects 1 product.


Products: Belden Hirschmann Bat-C2 Firmware.

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

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

## Is CVE-2022-40282 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40282 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40282 is a high-severity command injection vulnerability in n/a, published on 25 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40282 exists.

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-40282/ (Markdown: https://insights.sbomify.com/CVE-2022-40282/index.md)
```

## Sources

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

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