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

> Remote attackers can execute arbitrary code on users running vulnerable moxftp clients by sending a maliciously long FTP banner.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-281, GHSA-q8mx-wr5c-627f

## What is CVE-2003-0203?

CVE-2003-0203 is a high-severity memory corruption vulnerability in n/a, published on 8 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in moxftp 2.2 and earlier allows remote malicious FTP servers to execute arbitrary code via a long FTP banner.

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

It affects 2 products.


Products: Moxftp Moxftp, Xftp Xftp.

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

Upgrade to a fixed version.

## Is CVE-2003-0203 being exploited?

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

Public exploit code:

- moxftp 2.2 - Banner Parsing Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0203 is a high-severity memory corruption vulnerability in n/a, published on 8 Apr 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0203 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-0203/ (Markdown: https://insights.sbomify.com/CVE-2003-0203/index.md)
```

## Sources

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

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