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

> A local authenticated privileged attacker can execute arbitrary code via the debug command in Douran DSGate.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2023
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-p8f2-pv69-c68g

## What is CVE-2023-38996?

CVE-2023-38996 is a medium-severity command injection vulnerability in n/a, published on 22 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in all versions of Douran DSGate allows a local authenticated privileged attacker to execute arbitrary code via the debug command.

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

It affects 1 product.


Products: Douran Dsgate.

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

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

## Is CVE-2023-38996 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38996 is a medium-severity command injection vulnerability in n/a, published on 22 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38996 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-38996/ (Markdown: https://insights.sbomify.com/CVE-2023-38996/index.md)
```

## Sources

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

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