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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious TiVo TY media file in VLC Media Player.

- **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:** Yes
- **Published:** 21 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-4654, GHSA-wrh9-pxv5-hf6w

## What is CVE-2008-4654?

CVE-2008-4654 is a critical memory corruption vulnerability in Videolan Vlc Media Player, published on 21 Oct 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

Stack-based buffer overflow in the parse_master function in the Ty demux plugin (modules/demux/ty.c) in VLC Media Player 0.9.0 through 0.9.4 allows remote attackers to execute arbitrary code via a TiVo TY media file with a header containing a crafted size value.

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

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

It affects 1 product.


Products: Videolan Vlc Media Player.

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

Upgrade to a fixed version.

## Is CVE-2008-4654 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-4654 exists.

Public exploit code:

- An EXP could run on Windows x64 against CVE-2008-4654. (github_poc): https://github.com/KernelErr/VLC-CVE-2008-4654-Exploit
- VideoLAN VLC Media Player 0.9.4 - '.TY' Local Stack Buffer Overflow (exploitdb)
- VideoLAN VLC TiVo Buffer Overflow (metasploit)
- VideoLAN VLC Media Player 0.9.4 - '.ty' Local Buffer Overflow (SEH) (exploitdb)
- VideoLAN VLC Media Player 0.9.4 - TiVo Buffer Overflow (Metasploit) (exploitdb)
- VideoLAN VLC media player 0.9.4 Media Player ty.c buffer overflow (github_poc): https://github.com/bongbongco/CVE-2008-4654

## Other vulnerabilities in Videolan Vlc Media Player

- [CVE-2008-0296](https://insights.sbomify.com/CVE-2008-0296/): Memory corruption in n/a (critical 10.0)
- [CVE-2023-47359](https://insights.sbomify.com/CVE-2023-47359/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-12874](https://insights.sbomify.com/CVE-2019-12874/): Use after free in n/a (critical 9.8)
- [CVE-2017-10699](https://insights.sbomify.com/CVE-2017-10699/): Memory corruption in n/a (critical 9.8)
- [CVE-2013-1868](https://insights.sbomify.com/CVE-2013-1868/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4654 is a critical memory corruption vulnerability in Videolan Vlc Media Player, published on 21 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-4654 exists.

Affected product: Videolan Vlc Media Player. 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-4654/ (Markdown: https://insights.sbomify.com/CVE-2008-4654/index.md)
```

## Sources

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

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