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

> Attackers can cause a denial-of-service crash in Netis routers by manipulating the CONTENT_LENGTH variable in a CGI script.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 13 Aug 2025
- **Updated:** 14 Aug 2025
- **Also known as:** GHSA-p6xg-3q2x-vvrw

## What is CVE-2025-50635?

CVE-2025-50635 is a high-severity vulnerability in n/a, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A null pointer dereference vulnerability was discovered in Netis WF2780 v2.2.35445. The vulnerability exists in the FUN_0048a728 function of the cgitest.cgi file. Attackers can trigger this vulnerability by controlling the CONTENT_LENGTH variable, causing the program to crash and potentially leading to a denial-of-service (DoS) attack.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Netis-Systems Wf2780 Firmware.

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

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

## Is CVE-2025-50635 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-25850](https://insights.sbomify.com/CVE-2024-25850/): Command injection in n/a (critical 9.8)
- [CVE-2024-25851](https://insights.sbomify.com/CVE-2024-25851/): Command injection in n/a (high 8.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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