Freefloat Ftp ServerApplication · Freefloat

CVE-2025-5664

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in FreeFloat FTP Server 1.0 and classified as critical. This issue affects some unknown processing of the component RESTART Command Handler. The manipulation leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

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 · high confidence

A buffer overflow vulnerability exists in the RESTART command handler of FreeFloat FTP Server 1.0, allowing remote attackers to potentially execute arbitrary code due to improper bounds checking when processing the RESTART command. The public exploit availability and CVSS 9.8 score indicate immediate exploitation risk.

MitigationSince FreeFloat FTP Server is abandoned and no patch is available, migrate to a supported FTP server (e.g., FileZilla Server, ProFTPD) and implement network-level access controls to reduce attack surface until migration is complete.

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
Freefloat Ftp ServerApplication
Affected:= 1.0

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FreeFloat FTP Server is installed
    Check running processes for 'freefloat.exe' or look for FreeFloat FTP Server in installed programs via Control Panel > Programs and Features
    Affected if FreeFloat FTP Server is present on the system
  2. Verify the installed version is 1.0
    Right-click the FreeFloat executable, select Properties, and check the Details tab for version information, or run 'freefloat.exe -v' if a version flag is supported
    Affected if Version is exactly 1.0
  3. Confirm the FTP service is running and accessible
    Run 'netstat -an | findstr :21' to check if port 21 is listening, or use Telnet or an FTP client to connect to the server
    Affected if FTP service is listening on any network interface (including localhost)
  4. Check if RESTART command is functional
    Connect to the FTP server and issue the 'REST' command followed by a byte offset (e.g., 'REST 100') to see if the server accepts it
    Affected if The REST command is accepted and responds without error

If FreeFloat FTP Server version 1.0 is running and the REST command is accessible (even on localhost), the environment is affected by CVE-2025-5664.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since FreeFloat FTP Server is abandoned and no patch is available, migrate to a supported FTP server (e.g., FileZilla Server, ProFTPD) and implement network-level access controls to reduce attack surface until migration is complete.

Fix this in Freefloat Ftp Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5664 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5664 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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