# CVE-2008-6079: Memory corruption in n/a

> Attackers can execute arbitrary code or cause denial of service via crafted image files processed by the imlib2 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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-6079, DSA-2029-1, GHSA-7hrq-pg32-qp7r

## What is CVE-2008-6079?

CVE-2008-6079 is a critical memory corruption vulnerability in n/a, published on 6 Feb 2009. 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

imlib2 before 1.4.2 allows context-dependent attackers to have an unspecified impact via a crafted (1) ARGB, (2) BMP, (3) JPEG, (4) LBM, (5) PNM, (6) TGA, or (7) XPM file, related to "several heap and stack based buffer overflows - partly due to integer overflows."

## Which versions are affected by CVE-2008-6079?

It affects 1 product.


Products: Enlightenment Imlib2.

## How do I fix CVE-2008-6079?

Upgrade to a fixed version.

## Is CVE-2008-6079 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12761](https://insights.sbomify.com/CVE-2020-12761/): Integer overflow in n/a (critical 9.1)
- [CVE-2024-25447](https://insights.sbomify.com/CVE-2024-25447/): Memory corruption in n/a (high 8.8)
- [CVE-2024-25448](https://insights.sbomify.com/CVE-2024-25448/): Memory corruption in n/a (high 8.8)
- [CVE-2024-25450](https://insights.sbomify.com/CVE-2024-25450/): Memory corruption in n/a (high 8.8)
- [CVE-2008-5187](https://insights.sbomify.com/CVE-2008-5187/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6079 and fix it if it is affected.

What it is: CVE-2008-6079 is a critical memory corruption vulnerability in n/a, published on 6 Feb 2009. 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: There is no known exploitation of CVE-2008-6079 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-2008-6079/ (Markdown: https://insights.sbomify.com/CVE-2008-6079/index.md)
```

## Sources

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

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