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

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

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-35403?

CVE-2024-35403 is a low-severity memory corruption vulnerability in n/a, published on 28 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

TOTOLINK CP900L v4.1.5cu.798_B20221228 was discovered to contain a stack overflow via the desc parameter in the function setIpPortFilterRules

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

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

It affects 1 product.


Products: Totolink Cp900l Firmware.

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

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

## Is CVE-2024-35403 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-35398](https://insights.sbomify.com/CVE-2024-35398/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-35396](https://insights.sbomify.com/CVE-2024-35396/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2024-35397](https://insights.sbomify.com/CVE-2024-35397/): Command injection in n/a (high 8.8)
- [CVE-2024-35399](https://insights.sbomify.com/CVE-2024-35399/): Memory corruption in n/a (high 8.8)
- [CVE-2024-35395](https://insights.sbomify.com/CVE-2024-35395/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35403 is a low-severity memory corruption vulnerability in n/a, published on 28 May 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-2024-35403 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-35403/ (Markdown: https://insights.sbomify.com/CVE-2024-35403/index.md)
```

## Sources

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

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