# CVE-2022-44373: Memory corruption in n/a

> A stack overflow in TrendNet TEW-820AP allows remote attackers to execute arbitrary code on the device.

- **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:** 7 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-6r4x-cgfq-6wg5

## What is CVE-2022-44373?

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

### Official description

A stack overflow vulnerability exists in TrendNet Wireless AC Easy-Upgrader TEW-820AP (Version v1.0R, firmware version 1.01.B01) which may result in remote code execution.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Trendnet Tew-820ap Firmware.

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

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

## Is CVE-2022-44373 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44373 exists.

## Other vulnerabilities in n/a

- [CVE-2024-50667](https://insights.sbomify.com/CVE-2024-50667/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-47065](https://insights.sbomify.com/CVE-2022-47065/): Memory corruption in n/a (high 8.8)
- [CVE-2023-24095](https://insights.sbomify.com/CVE-2023-24095/): Memory corruption in n/a (high 8.8)
- [CVE-2023-24096](https://insights.sbomify.com/CVE-2023-24096/): Memory corruption in n/a (high 8.8)
- [CVE-2023-24097](https://insights.sbomify.com/CVE-2023-24097/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44373 is a high-severity memory corruption vulnerability in n/a, published on 7 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44373 exists.

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-44373/ (Markdown: https://insights.sbomify.com/CVE-2022-44373/index.md)
```

## Sources

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

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