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

> Attackers can cause a Denial of Service on Tenda AC1206 routers via a crafted POST request exploiting a buffer overflow.

- **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:** 30 Jun 2025
- **Updated:** 30 Jun 2025
- **Also known as:** GHSA-5gp4-4qmw-fhf4

## What is CVE-2024-53621?

CVE-2024-53621 is a high-severity memory corruption vulnerability in n/a, published on 30 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow in the formSetCfm() function of Tenda AC1206 1200M 11ac US_AC1206V1.0RTL_V15.03.06.23_multi_TD01 allows attackers to cause a Denial of Service (DoS) via a crafted POST request.

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

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


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

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

## Is CVE-2024-53621 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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