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

> A buffer overflow in the webproc cgi allows attackers to execute arbitrary code on the D-Link DSL-3788 router.

- **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:** 20 Mar 2025
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-j48m-433v-3q7r

## What is CVE-2024-57440?

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

### Official description

D-Link DSL-3788 revA1 1.01R1B036_EU_EN is vulnerable to Buffer Overflow via the COMM_MAKECustomMsg function of the webproc cgi

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

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

It affects 1 product.


Products: Dlink Dsl-3788 Firmware.

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

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

## Is CVE-2024-57440 being exploited?

There is no known exploitation of CVE-2024-57440 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57440 is a high-severity memory corruption vulnerability in n/a, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-57440 in the wild and no public exploit code.

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-57440/ (Markdown: https://insights.sbomify.com/CVE-2024-57440/index.md)
```

## Sources

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

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