# CVE-2020-24365: Command injection in n/a

> Authenticated attackers can execute arbitrary commands as root on Gemtek routers via the Monitor Diagnostic network page, especially if default credentials are used.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3876-gmcv-479m

## What is CVE-2020-24365?

CVE-2020-24365 is a high-severity command injection vulnerability in n/a, published on 24 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Gemtek WRTM-127ACN 01.01.02.141 and WRTM-127x9 01.01.02.127 devices. The Monitor Diagnostic network page allows an authenticated attacker to execute a command directly on the target machine. Commands are executed as the root user (uid 0). (Even if a login is required, most routers are left with default credentials.)

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2020-24365?

It affects 2 products.


Products: Gemteks Wrtm-127acn Firmware, Gemteks Wrtm-127x9 Firmware.

## How do I fix CVE-2020-24365?

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

## Is CVE-2020-24365 being exploited?

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

Public exploit code:

- Gemtek WVRTM-127ACN 01.01.02.141 - Authenticated Arbitrary Command Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24365 and fix it if it is affected.

What it is: CVE-2020-24365 is a high-severity command injection vulnerability in n/a, published on 24 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24365 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-2020-24365/ (Markdown: https://insights.sbomify.com/CVE-2020-24365/index.md)
```

## Sources

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

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