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

> Local attackers can exploit a buffer overflow in the rlpr daemon to execute arbitrary code and escalate privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0454, GHSA-pjrr-69h2-f25x

## What is CVE-2004-0454?

CVE-2004-0454 is a high-severity memory corruption vulnerability in n/a, published on 30 Jun 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in the msg function for rlpr daemon (rlprd) 2.04 allows local users to execute arbitrary code.

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

It affects 1 product.


Products: Rlpr Rlpr.

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

Apply the vendor's patch.

## Is CVE-2004-0454 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0393](https://insights.sbomify.com/CVE-2004-0393/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0454 is a high-severity memory corruption vulnerability in n/a, published on 30 Jun 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0454 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-2004-0454/ (Markdown: https://insights.sbomify.com/CVE-2004-0454/index.md)
```

## Sources

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

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