CVE-2020-37067
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFiletto 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Filetto 1.0 FTP server contains a buffer overflow vulnerability in its FEAT command handler. Attackers can trigger a denial of service by sending an oversized FEAT command containing 11,008 bytes of repeated characters, which causes the service to crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Filetto FTP server installationCheck if Filetto FTP server is installed on the system. Look for the executable or service named 'Filetto' or check common installation directories. On Windows, check Program Files; on Linux/Unix, check /usr/local/filetto or similar paths.Affected if Filetto FTP server version 1.0 is installed and running
-
Confirm the installed version is 1.0Run the Filetto executable with version flag (typically 'filetto -v' or check the service properties) to obtain the exact version number. Compare against the affected version 1.0.Affected if The installed version is Filetto 1.0 exactly
-
Verify FTP service is runningCheck if the Filetto FTP service is active and accepting connections. Use commands like 'netstat' or 'ss' to confirm port 21 is listening, or check service status through the system service manager.Affected if The Filetto FTP service is running and listening on FTP port (default 21)
-
Confirm FEAT command is processedConnect to the FTP server using any FTP client and issue the FEAT command to verify the server processes this command. A response from the server confirms the FEAT handler is active.Affected if The FTP server responds to the FEAT command, indicating the vulnerable handler is enabled
You are affected if Filetto version 1.0 is installed, the FTP service is running, and the FEAT command handler is active and processing requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThe vulnerability requires patching the FEAT command processing to implement proper input validation and bounds checking. Until an official patch is available, network-level access controls or disabling the FTP service can reduce exposure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-37067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-37067 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data