# CVE-2024-27619: Denial of service in n/a

> An attacker with FTP access can cause a router crash and reboot by uploading large files that exhaust system memory.

- **Severity:** High 7.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-3cp6-m65f-qhcw

## What is CVE-2024-27619?

CVE-2024-27619 is a high-severity denial of service vulnerability in n/a, published on 29 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dlink Dir-3040us A1 1.20b03a hotfix is vulnerable to Buffer Overflow. Any user having read/write access to ftp server can write directly to ram causing buffer overflow if file or files uploaded are greater than available ram. Ftp server allows change of directory to root which is one level up than root of usb flash directory. During upload ram is getting filled and causing system resource exhaustion (no free memory) which causes system to crash and reboot.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2024-27619 being exploited?

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

Public exploit code:

- CVE-2024-27619 (github_poc): https://github.com/ioprojecton/dir-3040_dos

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27619 is a high-severity denial of service vulnerability in n/a, published on 29 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27619 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-27619/ (Markdown: https://insights.sbomify.com/CVE-2024-27619/index.md)
```

## Sources

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

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