Client crash via oversized account-field buffer
Published Feb 6, 2026 · Updated Feb 6, 2026
Classic buffer overflow in Core FTP LE 2.2 build 1947 allows local users to crash the client through an oversized account value. The Connect dialog's Advanced pane copies a 20,000-character Account value without enforcing the destination buffer's size. Triggering requires local interaction with the Windows client; the process exits, and subsequent attempts to launch the client fail.
Summary
What happened
Classic buffer overflow in Core FTP LE 2.2 build 1947 allows local users to crash the client through an oversized account value. The Connect dialog's Advanced pane copies a 20,000-character Account value without enforcing the destination buffer's size. Triggering requires local interaction with the Windows client; the process exits, and subsequent attempts to launch the client fail.
The record
- CVE
- CVE-2020-37107
- Published
- Feb 6, 2026
- Updated
- Feb 6, 2026
- Vendor
- Core FTP
- Product
- Core FTP LE
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2026CVE publishedPublication date reported by the CVE source.
- Feb 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.2 build 1947
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Core FTP LE 2.2 - Denial of Service (PoC)proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo