# CVE-2025-57623: Null dereference in n/a

> A NULL pointer dereference in TOTOLINK N600R firmware allows attackers to cause a Denial of Service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-6wx9-5wq9-rr87

## What is CVE-2025-57623?

CVE-2025-57623 is a medium-severity vulnerability in n/a, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A NULL pointer dereference in TOTOLINK N600R firmware v4.3.0cu.7866_B2022506 allows attackers to cause a Denial of Service.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Totolink N600r Firmware.

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

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

## Is CVE-2025-57623 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-51390](https://insights.sbomify.com/CVE-2025-51390/): Command injection in n/a (critical 9.8)
- [CVE-2025-46060](https://insights.sbomify.com/CVE-2025-46060/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-22900](https://insights.sbomify.com/CVE-2025-22900/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28905](https://insights.sbomify.com/CVE-2022-28905/): Command injection in n/a (critical 9.8)
- [CVE-2022-28906](https://insights.sbomify.com/CVE-2022-28906/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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