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

> Attackers can execute arbitrary commands on Delta Electronics DX-2100 devices via the net_diagnose function.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-83hh-2xcw-p8rr

## What is CVE-2022-42140?

CVE-2022-42140 is a high-severity command injection vulnerability in n/a, published on 13 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Delta Electronics DX-2100-L1-CN 2.42 is vulnerable to Command Injection via lform/net_diagnose.

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

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

It affects 1 product.


Products: Deltaww Dx-2100-L1-Cn Firmware.

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

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

## Is CVE-2022-42140 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-42141](https://insights.sbomify.com/CVE-2022-42141/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42140 is a high-severity command injection vulnerability in n/a, published on 13 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-42140 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-42140/ (Markdown: https://insights.sbomify.com/CVE-2022-42140/index.md)
```

## Sources

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

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