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

> Remote attackers can execute arbitrary code via crafted media files due to heap-based buffer overflows in the xine-lib media library.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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-3jxv-2g3q-q23g

## What is CVE-2008-5236?

CVE-2008-5236 is a critical memory corruption 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 heap-based buffer overflows in xine-lib 1.1.12, and other 1.1.15 and earlier versions, allow remote attackers to execute arbitrary code via vectors related to (1) a crafted EBML element length processed by the parse_block_group function in demux_matroska.c; (2) a certain combination of sps, w, and h values processed by the real_parse_audio_specific_data and demux_real_send_chunk functions in demux_real.c; and (3) an unspecified combination of three values processed by the open_ra_file function in demux_realaudio.c.  NOTE: vector 2 reportedly exists because of an incomplete fix in 1.1.15.

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

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

It affects 1 product.


Products: Xine Xine.

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

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

## Is CVE-2008-5236 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5237](https://insights.sbomify.com/CVE-2008-5237/): Integer overflow in n/a (critical 10.0)
- [CVE-2008-5235](https://insights.sbomify.com/CVE-2008-5235/): 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-5236 and fix it if it is affected.

What it is: CVE-2008-5236 is a critical memory corruption 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-5236 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-5236/ (Markdown: https://insights.sbomify.com/CVE-2008-5236/index.md)
```

## Sources

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

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