CVE-2019-25614
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 · uneditedFree Float FTP 1.0 contains a buffer overflow vulnerability in the STOR command handler that allows remote attackers to execute arbitrary code by sending a crafted STOR request with an oversized payload. Attackers can authenticate with anonymous credentials and send a malicious STOR command containing 247 bytes of padding followed by a return address and shellcode to trigger code execution on the FTP server.
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 confidenceFree Float FTP 1.0 suffers from a buffer overflow in its STOR command handler. Attackers with anonymous FTP access can send a specially crafted STOR request containing 247 bytes of padding, followed by a return address and shellcode, to achieve remote code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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.
-
Identify if Free Float FTP Server is installedCheck for the presence of Free Float FTP Server executable (typically at C:\Program Files\FreeFloat\FreeFloat FTP Server.exe or C:\FreeFloat\FreeFloat FTP Server.exe) or check Windows Services for 'FreeFloat FTP Server'Affected if Free Float FTP Server executable or service is found on the system
-
Verify the installed version is 1.0Right-click the FreeFloat FTP Server.exe file, select Properties, and check the Version tab; or run the executable and check the banner/version displayedAffected if Version is exactly 1.0 (the only affected version)
-
Confirm the FTP service is runningOpen Windows Services console (services.msc) and check if 'FreeFloat FTP Server' status is Running, or use command: net start | findstr -i FreeFloatAffected if The Free Float FTP Server service is currently running
-
Check if anonymous authentication is enabledConnect to the FTP server locally or remotely (ftp localhost) and attempt to log in with username 'anonymous' and any email address as password; or check the server configuration for anonymous access settingsAffected if Anonymous login succeeds without valid credentials (this is required for remote exploitation)
User is affected if Free Float FTP Server version 1.0 is installed, the service is running, and anonymous authentication is enabled, as all three conditions are required for the buffer overflow vulnerability to be exploitable.
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 dataReplace Free Float FTP 1.0 with a actively maintained FTP server solution, or if replacement is not immediately feasible, disable the FTP service and restrict network access until migration is complete.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25614 — 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-2019-25614 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