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

> Attackers can execute arbitrary system commands on Tenhot TWS-100 routers via the network diagnostic component, leading to remote code execution.

- **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:** No
- **Published:** 15 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v4r7-qcrq-8vp4

## What is CVE-2022-37861?

CVE-2022-37861 is a critical command injection vulnerability in n/a, published on 15 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a remote code execution (RCE) vulnerability in Tenhot TWS-100 V4.0-201809201424 router device. It is necessary to know that the device account password is allowed to escape the execution system command through the network tools in the network diagnostic component.

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

It affects 1 product.


Products: Tenhot Tws-100 Firmware.

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

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

## Is CVE-2022-37861 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37861 is a critical command injection vulnerability in n/a, published on 15 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-37861 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-2022-37861/ (Markdown: https://insights.sbomify.com/CVE-2022-37861/index.md)
```

## Sources

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

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