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

> Remote attackers can execute arbitrary commands on TRENDnet routers via crafted POST requests to the apply.cgi binary.

- **Severity:** High 7.2 (`CVSS:3.0/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:** 20 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x2pr-pw9j-g89x

## What is CVE-2018-19239?

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

### Official description

TRENDnet TEW-673GRU v1.00b40 devices have an OS command injection vulnerability in the start_arpping function of the timer binary, which allows remote attackers to execute arbitrary commands via three parameters (dhcpd_start, dhcpd_end, and lan_ipaddr) passed to the apply.cgi binary through a POST request.

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

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

It affects 1 product.


Products: Trendnet Tew-673gru Firmware.

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

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

## Is CVE-2018-19239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19239 is a high-severity command injection vulnerability in n/a, published on 20 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19239 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-19239/ (Markdown: https://insights.sbomify.com/CVE-2018-19239/index.md)
```

## Sources

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

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