# CVE-2023-7219: Totolink N350RT cstecgi.cgi loginAuth stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the loginAuth function of Totolink N350RT routers, potentially leading to arbitrary code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-r29q-cjqw-pv7v

## What is CVE-2023-7219?

CVE-2023-7219 is a high-severity memory corruption vulnerability in Totolink N350RT, published on 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been found in Totolink N350RT 9.3.5u.6139_B202012 and classified as critical. Affected by this vulnerability is the function loginAuth of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument http_host leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-249853 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-7219?

It affects 1 product.


Products: Totolink N350rt Firmware.

## How do I fix CVE-2023-7219?

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

## Is CVE-2023-7219 being exploited?

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

## Other vulnerabilities in Totolink N350RT

- [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-2023-7219 and fix it if it is affected.

What it is: CVE-2023-7219 is a high-severity memory corruption vulnerability in Totolink N350RT, published on 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7219 exists.

Affected product: Totolink N350RT. 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-2023-7219/ (Markdown: https://insights.sbomify.com/CVE-2023-7219/index.md)
```

## Sources

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

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