# CVE-2018-19242: Memory corruption in n/a

> Authenticated attackers can execute arbitrary code on TRENDnet routers via a buffer overflow in the apply.cgi endpoint.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 20 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x39m-5345-h729

## What is CVE-2018-19242?

CVE-2018-19242 is a high-severity memory corruption vulnerability in n/a, published on 20 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in apply.cgi on TRENDnet TEW-632BRP 1.010B32 and TEW-673GRU devices allows attackers to hijack the control flow to any attacker-specified location by crafting a POST request payload (with authentication).

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Trendnet Tew-632brp Firmware, Trendnet Tew-673gru Firmware.

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

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

## Is CVE-2018-19242 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-57590](https://insights.sbomify.com/CVE-2024-57590/): Command injection in n/a (critical 9.8)
- [CVE-2019-11418](https://insights.sbomify.com/CVE-2019-11418/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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