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

> Remote attackers can execute arbitrary code via a malicious ARJ archive with long filenames, affecting users of the unarj library.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** Yes
- **Published:** 24 Nov 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xjjv-8746-3g86

## What is CVE-2004-0947?

CVE-2004-0947 is a critical memory corruption vulnerability in Gentoo Linux, published on 24 Nov 2004. 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 unarj before 2.63a-r2 allows remote attackers to execute arbitrary code via an arj archive that contains long filenames.

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

It affects 3 products.


Products: Arj Software Inc. Unarj, Gentoo Linux, Suse Suse Linux.

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

Upgrade to a fixed version.

## Is CVE-2004-0947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0947 is a critical memory corruption vulnerability in Gentoo Linux, published on 24 Nov 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-0947 in the wild and no public exploit code.

Affected product: Gentoo Linux. 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-0947/ (Markdown: https://insights.sbomify.com/CVE-2004-0947/index.md)
```

## Sources

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

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