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

> Remote attackers can execute arbitrary code via buffer overflows in Metamail, requiring immediate upgrades to secure email processing systems.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xp3c-x693-rrgv

## What is CVE-2004-0105?

CVE-2004-0105 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 19 Feb 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in Metamail 2.7 and earlier allow remote attackers to execute arbitrary code.

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

It affects 4 products.


Products: Metamail Corporation Metamail, Redhat Enterprise Linux, Redhat Linux Advanced Workstation, Sgi Propack.

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

Upgrade to a fixed version.

## Is CVE-2004-0105 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2006-0709](https://insights.sbomify.com/CVE-2006-0709/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0104](https://insights.sbomify.com/CVE-2004-0104/): Other in n/a (high 7.5)
- [CVE-1999-1261](https://insights.sbomify.com/CVE-1999-1261/): Memory corruption in n/a (medium 5.0)
- [CVE-1999-1266](https://insights.sbomify.com/CVE-1999-1266/): Information disclosure in n/a (medium 5.0)
- [CVE-1999-1263](https://insights.sbomify.com/CVE-1999-1263/): Path traversal in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0105 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 19 Feb 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0105 in the wild and no public exploit code.

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

## Sources

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

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