# CVE-2003-0831: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in ProFTPD's ASCII mode file transfer handling.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wmjc-5j86-p959

## What is CVE-2003-0831?

CVE-2003-0831 is a critical memory corruption vulnerability in n/a, published on 25 Sep 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ProFTPD 1.2.7 through 1.2.9rc2 does not properly translate newline characters when transferring files in ASCII mode, which allows remote attackers to execute arbitrary code via a buffer overflow using certain files.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2003-0831?

It affects 1 product.


Products: Proftpd Project Proftpd.

## How do I fix CVE-2003-0831?

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

## Is CVE-2003-0831 being exploited?

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

Public exploit code:

- ProFTPd 1.2.7/1.2.8 - '.ASCII' File Transfer Buffer Overrun (exploitdb)
- ProFTPd 1.2.9 rc2 - '.ASCII' File Remote Code Execution (1) (exploitdb)
- ProFTPd 1.2.7 < 1.2.9rc2 - Remote Code Execution / Brute Force (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5815](https://insights.sbomify.com/CVE-2006-5815/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0500](https://insights.sbomify.com/CVE-2003-0500/): SQL injection in n/a (critical 10.0)
- [CVE-1999-0911](https://insights.sbomify.com/CVE-1999-0911/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0542](https://insights.sbomify.com/CVE-2009-0542/): SQL injection in n/a (high 7.5)
- [CVE-2005-4816](https://insights.sbomify.com/CVE-2005-4816/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0831 and fix it if it is affected.

What it is: CVE-2003-0831 is a critical memory corruption vulnerability in n/a, published on 25 Sep 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0831 exists.

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-2003-0831/ (Markdown: https://insights.sbomify.com/CVE-2003-0831/index.md)
```

## Sources

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

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