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

> Remote attackers with administrator privileges can execute arbitrary code via a buffer overflow in the RedirectAll 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:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wr5j-574c-4wp4

## What is CVE-2004-1127?

CVE-2004-1127 is a critical memory corruption vulnerability in n/a, published on 5 Dec 2004. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Buffer overflow in Open Dc Hub 0.7.14 allows remote attackers, with administrator privileges, to execute arbitrary code via a long RedirectAll command.

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

It affects 1 product.


Products: Open Dc Hub Direct Connect Peer-to-Peer Client.

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

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

## Is CVE-2004-1127 being exploited?

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

Public exploit code:

- Open DC Hub 0.7.14 - Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1127 is a critical memory corruption vulnerability in n/a, published on 5 Dec 2004. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1127 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-1127/ (Markdown: https://insights.sbomify.com/CVE-2004-1127/index.md)
```

## Sources

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

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