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

> Remote attackers can crash VLC media player by tricking users into opening a crafted Cinepak file, causing memory corruption.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 24 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1769, GHSA-mxxw-w2hq-pvjj

## What is CVE-2008-1769?

CVE-2008-1769 is a medium-severity memory corruption vulnerability in n/a, published on 24 Apr 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

VLC before 0.8.6f allow remote attackers to cause a denial of service (crash) via a crafted Cinepak file that triggers an out-of-bounds array access and memory corruption.

Weakness: CWE-399

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

It affects 1 product.


Products: Videolan Vlc.

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

Upgrade to a fixed version.

## Is CVE-2008-1769 being exploited?

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

Public exploit code:

- Kantaris 0.3.4 - SSA Subtitle Local Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-6440](https://insights.sbomify.com/CVE-2014-6440/): Memory corruption in n/a (critical 9.8)
- [CVE-2007-6681](https://insights.sbomify.com/CVE-2007-6681/): Memory corruption in n/a (high 7.5)
- [CVE-2007-6682](https://insights.sbomify.com/CVE-2007-6682/): Code injection in n/a (high 7.5)
- [CVE-2008-1768](https://insights.sbomify.com/CVE-2008-1768/): Integer overflow in n/a (medium 6.8)
- [CVE-2008-1881](https://insights.sbomify.com/CVE-2008-1881/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1769 is a medium-severity memory corruption vulnerability in n/a, published on 24 Apr 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-1769 exists.

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-1769/ (Markdown: https://insights.sbomify.com/CVE-2008-1769/index.md)
```

## Sources

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

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