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

> Remote malicious FTP servers can execute arbitrary code on Crystal FTP Client users via a buffer overflow triggered by long file extensions in LIST responses.

- **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:** No
- **Published:** 6 Jan 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x7w7-f2hw-89jv

## What is CVE-2004-1327?

CVE-2004-1327 is a high-severity memory corruption vulnerability in n/a, published on 6 Jan 2005. 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 Crystal FTP Client 2.8 allows remote malicious servers to execute arbitrary code via a response to a LIST command that contains a file name with a long extension.

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

It affects 1 product.


Products: Crystal Art Software Crystal Ftp.

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

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

## Is CVE-2004-1327 being exploited?

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

Public exploit code:

- CrystalFTP Pro 2.8 - Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1327 is a high-severity memory corruption vulnerability in n/a, published on 6 Jan 2005. 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-2004-1327 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-2004-1327/ (Markdown: https://insights.sbomify.com/CVE-2004-1327/index.md)
```

## Sources

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

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