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

> A stack overflow in the Tenda G3 router allows attackers to execute arbitrary code or cause a denial of service via the formSetPortMapping function.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-r44r-7g3x-49c3

## What is CVE-2024-50854?

CVE-2024-50854 is a high-severity memory corruption vulnerability in n/a, published on 13 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tenda G3 v3.0 v15.11.0.20 was discovered to contain a stack overflow via the formSetPortMapping function.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Tendacn G3 Firmware.

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

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

## Is CVE-2024-50854 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-50852](https://insights.sbomify.com/CVE-2024-50852/): Command injection in n/a (high 8.8)
- [CVE-2024-50853](https://insights.sbomify.com/CVE-2024-50853/): Command injection in n/a (high 8.8)
- [CVE-2024-8224](https://insights.sbomify.com/CVE-2024-8224/): Tenda G3 setDebugCfg formSetDebugCfg stack-based overflow (high 8.7)
- [CVE-2024-46628](https://insights.sbomify.com/CVE-2024-46628/): Command injection in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50854 is a high-severity memory corruption vulnerability in n/a, published on 13 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50854 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-50854/ (Markdown: https://insights.sbomify.com/CVE-2024-50854/index.md)
```

## Sources

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

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