# CVE-2018-0541: Memory corruption in Tiny FTP Daemon

> A buffer overflow in Tiny FTP Daemon allows attackers to execute arbitrary code or cause a denial-of-service condition.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 22 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-77mc-88cx-8g8x

## What is CVE-2018-0541?

CVE-2018-0541 is a critical memory corruption vulnerability in Hisayuki Nomura Tiny FTP Daemon, published on 22 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in Tiny FTP Daemon Ver0.52d allows an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code via unspecified vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-0541?

It affects 1 product.


Products: Tinyftp Project Tinyftp.

## How do I fix CVE-2018-0541?

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

## Is CVE-2018-0541 being exploited?

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

## Other vulnerabilities in Hisayuki Nomura Tiny FTP Daemon

- [CVE-2018-17106](https://insights.sbomify.com/CVE-2018-17106/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0541 and fix it if it is affected.

What it is: CVE-2018-0541 is a critical memory corruption vulnerability in Hisayuki Nomura Tiny FTP Daemon, published on 22 Mar 2018. 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-2018-0541 in the wild and no public exploit code.

Affected product: Hisayuki Nomura Tiny FTP Daemon. 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-2018-0541/ (Markdown: https://insights.sbomify.com/CVE-2018-0541/index.md)
```

## Sources

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

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