# CVE-2019-25611: MiniFtp parseconf_load_setting Buffer Overflow via Configuration

> Local attackers can execute arbitrary code with root privileges by exploiting a buffer overflow in MiniFtp's configuration parser.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-jc9j-g669-vr2x

## What is CVE-2019-25611?

CVE-2019-25611 is a high-severity memory corruption vulnerability in skyqinsc MiniFtp, published on 22 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MiniFtp contains a buffer overflow vulnerability in the parseconf_load_setting function that allows local attackers to execute arbitrary code by supplying oversized configuration values. Attackers can craft a miniftpd.conf file with values exceeding 128 bytes to overflow stack buffers and overwrite the return address, enabling code execution with root privileges.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-25611?


## How do I fix CVE-2019-25611?

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

## Is CVE-2019-25611 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25611 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25611 and fix it if it is affected.

What it is: CVE-2019-25611 is a high-severity memory corruption vulnerability in skyqinsc MiniFtp, published on 22 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25611 exists.

Affected product: skyqinsc MiniFtp. 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-2019-25611/ (Markdown: https://insights.sbomify.com/CVE-2019-25611/index.md)
```

## Sources

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

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