# CVE-2004-0346: Memory corruption in n/a

> Local attackers can gain privileges via an off-by-one buffer overflow in the RETR command handling of ProFTPD.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-899x-jhm8-pc3m

## What is CVE-2004-0346?

CVE-2004-0346 is a high-severity memory corruption vulnerability in n/a, published on 18 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Off-by-one buffer overflow in _xlate_ascii_write() in ProFTPD 1.2.7 through 1.2.9rc2p allows local users to gain privileges via a 1024 byte RETR command.

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2004-0346?

It affects 1 product.


Products: Proftpd Proftpd.

## How do I fix CVE-2004-0346?

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

## Is CVE-2004-0346 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4221](https://insights.sbomify.com/CVE-2010-4221/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-20103](https://insights.sbomify.com/CVE-2010-20103/): ProFTPD 1.3.3c Backdoor Command Execution (critical 9.3)
- [CVE-2011-4130](https://insights.sbomify.com/CVE-2011-4130/): Use after free in n/a (critical 9.0)
- [CVE-2026-63090](https://insights.sbomify.com/CVE-2026-63090/): ProFTPD mod_sftp Heap Buffer Overflow via SFTP Packet Reassembly (high 8.7)
- [CVE-2026-35025](https://insights.sbomify.com/CVE-2026-35025/): ProFTPD ACL Bypass via /proc/self/root Path Prefix in RNFR (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0346 and fix it if it is affected.

What it is: CVE-2004-0346 is a high-severity memory corruption vulnerability in n/a, published on 18 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0346 in the wild and no public exploit code.

Affected product: n/a. 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-2004-0346/ (Markdown: https://insights.sbomify.com/CVE-2004-0346/index.md)
```

## Sources

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

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