# CVE-2025-45787: Memory corruption in n/a

> A buffer overflow in the TOTOLINK A3100R router allows attackers to execute arbitrary code or cause a denial of service via the comment parameter.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-wmr9-84fj-r9j8

## What is CVE-2025-45787?

CVE-2025-45787 is a medium-severity memory corruption vulnerability in n/a, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK A3100R V5.9c.1527 is vulnerable to Buffer Overflow viathe comment parameter in setIpPortFilterRules.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-45787?

It affects 1 product.


Products: Totolink A3100r Firmware.

## How do I fix CVE-2025-45787?

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

## Is CVE-2025-45787 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28256](https://insights.sbomify.com/CVE-2025-28256/): Command injection in n/a (critical 9.8)
- [CVE-2024-42546](https://insights.sbomify.com/CVE-2024-42546/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-42547](https://insights.sbomify.com/CVE-2024-42547/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-29644](https://insights.sbomify.com/CVE-2022-29644/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-29645](https://insights.sbomify.com/CVE-2022-29645/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-45787 and fix it if it is affected.

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

## Sources

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

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