# CVE-2025-5548: FreeFloat FTP Server NOOP Command buffer overflow

> Remote attackers can exploit a buffer overflow in the NOOP command handler of FreeFloat FTP Server to execute arbitrary code or cause denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-xc4j-qcg6-2m4x

## What is CVE-2025-5548?

CVE-2025-5548 is a medium-severity memory corruption vulnerability in FreeFloat FTP Server, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in FreeFloat FTP Server 1.0. Affected is an unknown function of the component NOOP Command Handler. The manipulation leads to buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-5548?

It affects 1 product.


Products: Freefloat Freefloat Ftp Server.

## How do I fix CVE-2025-5548?

No fix has been published for CVE-2025-5548 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5548 being exploited?

There is no known exploitation of CVE-2025-5548 in the wild and no public exploit code.

Public exploit code:

- Security research and technical analysis of CVE-2025-5548, a buffer overflow vulnerability affecting FreeFloat FTP Server 1.0. This repository documents vulnerability behavior, attack surface, controlled proof of concept testing, and defensive insights within a structured research environment for cybersecurity learning and analysis. (github_poc): https://github.com/mk017-hk/CVE-2025-5548
- Buffer overflow in FreeFloat FTP Server 1.0 illustrating how a single unsafe handler can generate multiple CVE entries across different commands. (github_poc): https://github.com/TheMalwareGuardian/CVE-2025-5548
- Freefloat FTP Server 1.0 - Remote Buffer Overflow (exploitdb)
- 🚀 Complete analysis and exploitation of CVE-2025-5548 (FreeFloat FTP Server 1.0 - NOOP Buffer Overflow)  Full methodology: manual tool installation, lab environment setup, fuzzing, offset calculation, bad chars, JMP ESP and working reverse shell exploit.   (github_poc): https://github.com/JSantos1990/CVE-2025-5548
- https://github.com/alanschmidt81/CVE-2025-5548 (github_poc): https://github.com/alanschmidt81/CVE-2025-5548
- Entorno y explotación de la vulnerabilidad CVE-2025-5548 (github_poc): https://github.com/javyan05/CVE-2025-5548

## Other vulnerabilities in FreeFloat FTP Server

- [CVE-2012-5106](https://insights.sbomify.com/CVE-2012-5106/): Memory corruption in n/a (critical 10.0)
- [CVE-2019-25614](https://insights.sbomify.com/CVE-2019-25614/): Free Float FTP 1.0 STOR Command Remote Buffer Overflow (critical 9.3)
- [CVE-2012-10030](https://insights.sbomify.com/CVE-2012-10030/): FreeFloat FTP Server Arbitrary File Upload (critical 9.3)
- [CVE-2012-10023](https://insights.sbomify.com/CVE-2012-10023/): FreeFloat FTP Server USER Command Buffer Overflow (medium 6.9)
- [CVE-2025-5664](https://insights.sbomify.com/CVE-2025-5664/): FreeFloat FTP Server RESTART Command buffer overflow (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5548 and fix it if it is affected.

What it is: CVE-2025-5548 is a medium-severity memory corruption vulnerability in FreeFloat FTP Server, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5548 in the wild and no public exploit code.

Affected product: FreeFloat FTP Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5548/ (Markdown: https://insights.sbomify.com/CVE-2025-5548/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5548
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5548
- OSV: https://osv.dev/vulnerability/CVE-2025-5548

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5548/
Summaries are generated and may contain mistakes; the official description above is the record.