# CVE-2020-37067: Filetto 1.0 - 'FEAT' Denial of Service

> Attackers can crash the Filetto FTP server by sending an oversized FEAT command, causing a denial of service.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-867q-8rpr-vpph

## What is CVE-2020-37067?

CVE-2020-37067 is a high-severity denial of service vulnerability in Utillyty Filetto, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Filetto 1.0 FTP server contains a denial of service vulnerability in the FEAT command processing that allows attackers to crash the service. Attackers can send an oversized FEAT command with 11,008 bytes of repeated characters to trigger a buffer overflow and terminate the FTP service.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2020-37067?


## How do I fix CVE-2020-37067?

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

## Is CVE-2020-37067 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37067 and fix it if it is affected.

What it is: CVE-2020-37067 is a high-severity denial of service vulnerability in Utillyty Filetto, published on 3 Feb 2026. 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-2020-37067 exists.

Affected product: Utillyty Filetto. 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-2020-37067/ (Markdown: https://insights.sbomify.com/CVE-2020-37067/index.md)
```

## Sources

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

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