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

> An authenticated attacker can trigger a buffer overflow in the setDiagnosisCfg function to potentially 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:** 23 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-v32r-mrmh-qxvx

## What is CVE-2022-44253?

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

### Official description

TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter ip in the setDiagnosisCfg function.

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

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

It affects 1 product.


Products: Totolink Lr350 Firmware.

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

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

## Is CVE-2022-44253 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-42967](https://insights.sbomify.com/CVE-2024-42967/): Information disclosure in n/a (critical 9.8)
- [CVE-2024-36783](https://insights.sbomify.com/CVE-2024-36783/): Command injection in n/a (critical 9.8)
- [CVE-2024-35387](https://insights.sbomify.com/CVE-2024-35387/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-35099](https://insights.sbomify.com/CVE-2024-35099/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-37145](https://insights.sbomify.com/CVE-2023-37145/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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