# CVE-2024-35387: Memory corruption in n/a

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

- **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:** 24 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-35387?

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

### Official description

TOTOLINK LR350 V9.3.5u.6369_B20220309 was discovered to contain a stack overflow via the http_host parameter in the function loginAuth.

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

## Which versions are affected by CVE-2024-35387?

It affects 1 product.


Products: Totolink Lr350 Firmware.

## How do I fix CVE-2024-35387?

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

## Is CVE-2024-35387 being exploited?

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

## 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-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)
- [CVE-2023-37146](https://insights.sbomify.com/CVE-2023-37146/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35387 and fix it if it is affected.

What it is: CVE-2024-35387 is a critical memory corruption vulnerability in n/a, published on 24 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35387 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-2024-35387/ (Markdown: https://insights.sbomify.com/CVE-2024-35387/index.md)
```

## Sources

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

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