CVE-2025-5667
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 · uneditedA vulnerability was found in FreeFloat FTP Server 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the component REIN Command Handler. The manipulation leads to buffer overflow. The attack may be launched 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 · moderate confidenceBuffer overflow vulnerability in the REIN command handler of FreeFloat FTP Server 1.0 allows remote attackers to overflow a buffer, potentially enabling remote code execution. The REIN command is used to reinitialize the FTP connection state, and improper bounds checking during handling enables the overflow.
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 FreeFloat FTP Server is installedCheck installed programs on the system or look for the executable (typically C:\Program Files\FreeFloat or similar paths). On Windows, review Add/Remove Programs or check for ftpserver.exe processes running.Affected if FreeFloat FTP Server executable is present on the system
-
Confirm the exact versionRight-click on the FreeFloat FTP Server executable (commonly named ftpserver.exe), select Properties, and check the Version tab. Alternatively, check the program's About or Help section.Affected if The installed version is FreeFloat FTP Server 1.0 exactly
-
Verify the FTP service is runningOpen Task Manager or use command 'tasklist /FI "IMAGENAME eq ftpserver.exe"' to check if the FTP server process is active.Affected if The FreeFloat FTP Server process is currently running
-
Check network exposureRun 'netstat -an | findstr :21' to determine if the FTP service is listening on port 21 and accessible from the network. Review firewall rules for inbound access to port 21.Affected if The FTP service is listening on a network-facing interface and accessible remotely
You are affected if FreeFloat FTP Server version 1.0 is installed and the service is running, particularly if exposed to network access, since the REIN command buffer overflow can be triggered remotely.
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 FreeFloat FTP Server with a currently maintained FTP server solution, or if continued use is required, implement network-level access controls to restrict FTP access to trusted IPs only while the software is being phased out.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5667 — 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-2025-5667 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