# CVE-2018-20841: Command injection in n/a

> Remote attackers can execute arbitrary commands on HooToo TripMate Titan routers by injecting shell metacharacters into the MAC address parameter.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 11 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3xfm-3jfc-q3c4

## What is CVE-2018-20841?

CVE-2018-20841 is a critical command injection vulnerability in n/a, published on 11 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HooToo TripMate Titan HT-TM05 and HT-05 routers with firmware 2.000.022 and 2.000.082 allow remote command execution via shell metacharacters in the mac parameter of a protocol.csp?function=set&fname=security&opt=mac_table request.

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

## Which versions are affected by CVE-2018-20841?

It affects 1 product.


Products: Hootoo Tripmate Titan Ht-Tm05 Firmware.

## How do I fix CVE-2018-20841?

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

## Is CVE-2018-20841 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20841 and fix it if it is affected.

What it is: CVE-2018-20841 is a critical command injection vulnerability in n/a, published on 11 Jun 2019. 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-2018-20841 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-2018-20841/ (Markdown: https://insights.sbomify.com/CVE-2018-20841/index.md)
```

## Sources

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

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