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

> Remote attackers can execute arbitrary code by tricking users into opening a crafted BMP file processed by the imlib library.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-548-2, GHSA-q46h-4c8m-gg49, RHSA-2004:465

## What is CVE-2004-0817?

CVE-2004-0817 is a high-severity memory corruption vulnerability in Conectiva Linux, published on 17 Sep 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

Multiple heap-based buffer overflows in the imlib BMP image handler allow remote attackers to execute arbitrary code via a crafted BMP file.

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

It affects 16 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `imlib` | Red Hat:enterprise_linux:3::as | All versions | 1:1.9.13-13.3 |
| `imlib-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:1.9.13-13.3 |
| `imlib-devel` | Red Hat:enterprise_linux:3::as | All versions | 1:1.9.13-13.3 |
| `imlib` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.9.13-13.3 |
| `imlib-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.9.13-13.3 |
| `imlib-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.9.13-13.3 |
| `imlib` | Red Hat:enterprise_linux:3::es | All versions | 1:1.9.13-13.3 |
| `imlib-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:1.9.13-13.3 |
| `imlib-devel` | Red Hat:enterprise_linux:3::es | All versions | 1:1.9.13-13.3 |
| `imlib` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.9.13-13.3 |
| `imlib-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.9.13-13.3 |
| `imlib-devel` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.9.13-13.3 |

Products: Conectiva Linux, Enlightenment Imlib, Enlightenment Imlib2, Imagemagick Imagemagick, Mandrakesoft Mandrake Linux, Mandrakesoft Mandrake Linux Corporate Server, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Fedora Core, Redhat Linux Advanced Workstation, Sun Java Desktop System, Suse Suse Linux, Turbolinux Turbolinux Desktop, Turbolinux Turbolinux Server, Turbolinux Turbolinux Workstation, Ubuntu Ubuntu Linux.

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

Apply the vendor's patch.

## Is CVE-2004-0817 being exploited?

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

## Other vulnerabilities in Conectiva Linux

- [CVE-2005-3625](https://insights.sbomify.com/CVE-2005-3625/): Denial of service in n/a (critical 10.0)
- [CVE-2004-0882](https://insights.sbomify.com/CVE-2004-0882/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0902](https://insights.sbomify.com/CVE-2004-0902/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0903](https://insights.sbomify.com/CVE-2004-0903/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0904](https://insights.sbomify.com/CVE-2004-0904/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0817 is a high-severity memory corruption vulnerability in Conectiva Linux, published on 17 Sep 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-0817 in the wild and no public exploit code.

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

## Sources

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

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