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

> A stack overflow in the TOTOLINK N600R router allows attackers to execute arbitrary code or cause a denial of service via the macAddress parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 10 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w89g-ch9p-2vjv

## What is CVE-2022-29394?

CVE-2022-29394 is a critical memory corruption vulnerability in n/a, published on 10 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK N600R V4.3.0cu.7647_B20210106 was discovered to contain a stack overflow via the macAddress parameter in the function FUN_0041b448.

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

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

It affects 1 product.


Products: Totolink N600r Firmware.

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

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

## Is CVE-2022-29394 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-51390](https://insights.sbomify.com/CVE-2025-51390/): Command injection in n/a (critical 9.8)
- [CVE-2025-46060](https://insights.sbomify.com/CVE-2025-46060/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-22900](https://insights.sbomify.com/CVE-2025-22900/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28905](https://insights.sbomify.com/CVE-2022-28905/): Command injection in n/a (critical 9.8)
- [CVE-2022-28906](https://insights.sbomify.com/CVE-2022-28906/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29394 is a critical memory corruption vulnerability in n/a, published on 10 May 2022. 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-2022-29394 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-2022-29394/ (Markdown: https://insights.sbomify.com/CVE-2022-29394/index.md)
```

## Sources

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

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