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

> Remote attackers can cause a denial of service on EvolutionX devices by sending long commands to the FTP or telnet servers.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-m4jp-mh99-vhwh

## What is CVE-2004-0268?

CVE-2004-0268 is a medium-severity memory corruption vulnerability in n/a, published on 18 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in EvolutionX 3921 and 3935 allow remote attackers to cause a denial of service (hang) via (1) a long cd command to the FTP server, or (2) a long dir command to the telnet server.

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

It affects 1 product.


Products: Evolutionx Evolutionx.

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

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

## Is CVE-2004-0268 being exploited?

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

Public exploit code:

- EvolutionX - Multiple Remote Buffer Overflow Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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