# CVE-2002-0826: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code via a buffer overflow in the WS_FTP FTP Server SITE CPWD command.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x5qx-v4p6-4p8f

## What is CVE-2002-0826?

CVE-2002-0826 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in WS_FTP FTP Server 3.1.1 allows remote authenticated users to execute arbitrary code via a long SITE CPWD command.

## Which versions are affected by CVE-2002-0826?

It affects 1 product.


Products: Progress Ws Ftp Server.

## How do I fix CVE-2002-0826?

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

## Is CVE-2002-0826 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-40044](https://insights.sbomify.com/CVE-2023-40044/): Progress WS_FTP Server Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2023-42657](https://insights.sbomify.com/CVE-2023-42657/): WS_FTP Server Directory Traversal (critical 9.9)
- [CVE-2023-42659](https://insights.sbomify.com/CVE-2023-42659/): WS_FTP Server Arbitrary File Upload (critical 9.1)
- [CVE-2008-0590](https://insights.sbomify.com/CVE-2008-0590/): Memory corruption in n/a (critical 9.0)
- [CVE-2023-40045](https://insights.sbomify.com/CVE-2023-40045/): WS_FTP Server Ad Hoc Transfer Module Reflected Cross-Site Scripting Vulnerability (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0826 and fix it if it is affected.

What it is: CVE-2002-0826 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0826 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-2002-0826/ (Markdown: https://insights.sbomify.com/CVE-2002-0826/index.md)
```

## Sources

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

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