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

> Attackers with file access can execute arbitrary OS commands via unsanitized status path script entries in OpenNDS.

- **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:** Yes
- **Published:** 26 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** DEBIAN-CVE-2023-38323, GHSA-c69w-p7cc-6h7c

## What is CVE-2023-38323?

CVE-2023-38323 is a critical command injection vulnerability in n/a, published on 26 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in OpenNDS before 10.1.3. It fails to sanitize the status path script entry in the configuration file, allowing attackers that have direct or indirect access to this file to execute arbitrary OS commands.

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

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

It affects 1 product.


Products: Opennds Opennds.

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

Upgrade to a fixed version.

## Is CVE-2023-38323 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-38317](https://insights.sbomify.com/CVE-2023-38317/): Command injection in n/a (critical 9.8)
- [CVE-2023-38318](https://insights.sbomify.com/CVE-2023-38318/): Command injection in n/a (critical 9.8)
- [CVE-2023-38319](https://insights.sbomify.com/CVE-2023-38319/): Command injection in n/a (critical 9.8)
- [CVE-2023-41101](https://insights.sbomify.com/CVE-2023-41101/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-41102](https://insights.sbomify.com/CVE-2023-41102/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38323 is a critical command injection vulnerability in n/a, published on 26 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38323 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-2023-38323/ (Markdown: https://insights.sbomify.com/CVE-2023-38323/index.md)
```

## Sources

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

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