# CVE-2020-37107: Core FTP LE 2.2 - Denial of Service

> Attackers can crash Core FTP LE by pasting a large buffer into the account field, causing the application to become unresponsive.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-3jf7-cmmw-4r75

## What is CVE-2020-37107?

CVE-2020-37107 is a medium-severity denial of service vulnerability in Core FTP LE, published on 6 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Core FTP LE 2.2 contains a denial of service vulnerability that allows attackers to crash the application by overwriting the account field with a large buffer. Attackers can create a text file with 20,000 repeated characters and paste it into the account field to cause the application to become unresponsive and require reinstallation.

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

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


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

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

## Is CVE-2020-37107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37107 is a medium-severity denial of service vulnerability in Core FTP LE, published on 6 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37107 exists.

Affected product: Core FTP LE. 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-37107/ (Markdown: https://insights.sbomify.com/CVE-2020-37107/index.md)
```

## Sources

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

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