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

> Remote authenticated users can execute arbitrary code via a buffer overflow in the Serv-U FTP server's MDTM command.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9cgv-5rj9-j8x4

## What is CVE-2004-0330?

CVE-2004-0330 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Serv-U ftp before 5.0.0.4 allows remote authenticated users to execute arbitrary code via a long time zone argument to the MDTM command.

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

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

It affects 1 product.


Products: Solarwinds Serv-U File Server.

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

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

## Is CVE-2004-0330 being exploited?

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

Public exploit code:

- RhinoSoft Serv-U FTPd Server 3/4/5 - 'MDTM' Time Argument Buffer Overflow (1) (exploitdb)
- RhinoSoft Serv-U FTPd Server 3/4/5 - 'MDTM' Time Argument Buffer Overflow (2) (exploitdb)
- RhinoSoft Serv-U FTPd Server 3/4/5 - 'MDTM' Time Argument Buffer Overflow (3) (exploitdb)
- RhinoSoft Serv-U FTPd Server 3/4/5 - MDTM Command Time Argument Buffer Overflow (4) (exploitdb)
- Serv-U FTPD MDTM Overflow (metasploit)
- RhinoSoft Serv-U FTPd Server 3.x/4.x/5.x - 'MDTM' Remote Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-4006](https://insights.sbomify.com/CVE-2009-4006/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-2532](https://insights.sbomify.com/CVE-2004-2532/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2011-4800](https://insights.sbomify.com/CVE-2011-4800/): Path traversal in n/a (critical 9.0)
- [CVE-2008-4501](https://insights.sbomify.com/CVE-2008-4501/): Path traversal in n/a (critical 9.0)
- [CVE-2004-2111](https://insights.sbomify.com/CVE-2004-2111/): Memory corruption in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0330 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0330 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-0330/ (Markdown: https://insights.sbomify.com/CVE-2004-0330/index.md)
```

## Sources

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

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