# CVE-2021-42324: Command injection in n/a

> Low-privileged authenticated attackers with physical access can execute root commands via shell metacharacters in the capture command parameters.

- **Severity:** High 7.4 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qjqv-pjh5-jmcf

## What is CVE-2021-42324?

CVE-2021-42324 is a high-severity command injection vulnerability in n/a, published on 5 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on DCN (Digital China Networks) S4600-10P-SI devices before R0241.0470. Due to improper parameter validation in the console interface, it is possible for a low-privileged authenticated attacker to escape the sandbox environment and execute system commands as root via shell metacharacters in the capture command parameters. Command output will be shown on the Serial interface of the device. Exploitation requires both credentials and physical access.

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

## Which versions are affected by CVE-2021-42324?

It affects 1 product.


Products: Dcnglobal S4600-10p-Si Firmware.

## How do I fix CVE-2021-42324?

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

## Is CVE-2021-42324 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42324 and fix it if it is affected.

What it is: CVE-2021-42324 is a high-severity command injection vulnerability in n/a, published on 5 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-42324 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-2021-42324/ (Markdown: https://insights.sbomify.com/CVE-2021-42324/index.md)
```

## Sources

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

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