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

> Attackers can execute arbitrary code by tricking users into opening a crafted ELF file with the file utility.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1304, GHSA-w22m-7gfq-73mf

## What is CVE-2004-1304?

CVE-2004-1304 is a critical memory corruption vulnerability in Gentoo Linux, published on 22 Dec 2004. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in the ELF header parsing code in file before 4.12 allows attackers to execute arbitrary code via a crafted ELF file.

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

It affects 3 products.


Products: File File, Gentoo Linux, Trustix Secure Linux.

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

Upgrade to a fixed version.

## Is CVE-2004-1304 being exploited?

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

Public exploit code:

- File ELF 4.x - Header Buffer Overflow (exploitdb)

## Other vulnerabilities in Gentoo Linux

- [CVE-2007-1536](https://insights.sbomify.com/CVE-2007-1536/): Integer overflow in n/a (critical 9.3)
- [CVE-2007-2799](https://insights.sbomify.com/CVE-2007-2799/): Integer overflow in n/a (medium 5.1)
- [CVE-2003-0102](https://insights.sbomify.com/CVE-2003-0102/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1304 is a critical memory corruption vulnerability in Gentoo Linux, published on 22 Dec 2004. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1304 exists.

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-1304/ (Markdown: https://insights.sbomify.com/CVE-2004-1304/index.md)
```

## Sources

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

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