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

> Remote attackers can execute arbitrary code or crash applications via crafted IFF ILBM files in SDL_image 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:** 1 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0544, GHSA-r37c-fgx7-q833

## What is CVE-2008-0544?

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

Heap-based buffer overflow in the IMG_LoadLBM_RW function in IMG_lbm.c in SDL_image before 1.2.7 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted IFF ILBM file.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Sdl Sdl Image.

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

Upgrade to a fixed version.

## Is CVE-2008-0544 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6697](https://insights.sbomify.com/CVE-2007-6697/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0544 is a critical memory corruption vulnerability in n/a, published on 1 Feb 2008. 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-2008-0544 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-0544/ (Markdown: https://insights.sbomify.com/CVE-2008-0544/index.md)
```

## Sources

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

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