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

> A stack overflow in the setDiagnosisCfg function allows attackers to execute arbitrary code or cause a denial of service on TOTOLINK N350RT routers.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f4j3-6hhj-67c6

## What is CVE-2022-36484?

CVE-2022-36484 is a high-severity memory corruption vulnerability in n/a, published on 25 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TOTOLINK N350RT V9.3.5u.6139_B20201216 was discovered to contain a stack overflow via the function setDiagnosisCfg.

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

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

It affects 1 product.


Products: Totolink N350rt Firmware.

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

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

## Is CVE-2022-36484 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-51630](https://insights.sbomify.com/CVE-2025-51630/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-42966](https://insights.sbomify.com/CVE-2024-42966/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-7462](https://insights.sbomify.com/CVE-2024-7462/): TOTOLINK N350RT cstecgi.cgi setWizardCfg buffer overflow (high 8.7)
- [CVE-2024-7333](https://insights.sbomify.com/CVE-2024-7333/): TOTOLINK N350RT cstecgi.cgi setParentalRules buffer overflow (high 8.7)
- [CVE-2022-36479](https://insights.sbomify.com/CVE-2022-36479/): Command injection in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36484 is a high-severity memory corruption vulnerability in n/a, published on 25 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36484 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-36484/ (Markdown: https://insights.sbomify.com/CVE-2022-36484/index.md)
```

## Sources

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

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