# CVE-2008-5237: Integer overflow in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted media files exploiting integer overflows in xine-lib.

- **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:** No
- **Published:** 26 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2rwr-j5mc-pp8c

## What is CVE-2008-5237?

CVE-2008-5237 is a critical vulnerability in n/a, published on 26 Nov 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

Multiple integer overflows in xine-lib 1.1.12, and other 1.1.15 and earlier versions, allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via (1) crafted width and height values that are not validated by the mymng_process_header function in demux_mng.c before use in an allocation calculation or (2) crafted current_atom_size and string_size values processed by the parse_reference_atom function in demux_qt.c for an RDRF_ATOM string.

Weakness: CWE-189

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

It affects 1 product.


Products: Xine Xine.

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

No fix has been published for CVE-2008-5237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-5237 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5235](https://insights.sbomify.com/CVE-2008-5235/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-5236](https://insights.sbomify.com/CVE-2008-5236/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0255](https://insights.sbomify.com/CVE-2007-0255/): Memory corruption in n/a (critical 9.3)
- [CVE-2006-1905](https://insights.sbomify.com/CVE-2006-1905/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1379](https://insights.sbomify.com/CVE-2004-1379/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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