# CVE-2023-43322: Command injection in n/a

> Attackers can execute arbitrary commands on ZPE Nodegrid OS via a vulnerable system toolkit file endpoint.

- **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:** 28 Oct 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-2vmv-m3hj-2wh8

## What is CVE-2023-43322?

CVE-2023-43322 is a high-severity command injection vulnerability in n/a, published on 28 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZPE Systems, Inc Nodegrid OS v5.0.0 to v5.0.17, v5.2.0 to v5.2.19, v5.4.0 to v5.4.16, v5.6.0 to v5.6.13, v5.8.0 to v5.8.10, and v5.10.0 to v5.10.3 was discovered to contain a command injection vulnerability via the endpoint /v1/system/toolkit/files/.

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

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

It affects 1 product.


Products: Zpesystems Nodegrid Os.

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

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

## Is CVE-2023-43322 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-44037](https://insights.sbomify.com/CVE-2023-44037/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43322 is a high-severity command injection vulnerability in n/a, published on 28 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-43322 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-2023-43322/ (Markdown: https://insights.sbomify.com/CVE-2023-43322/index.md)
```

## Sources

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

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