# CVE-2006-7222: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted FLI file in Media Player Classic.

- **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:** No
- **Published:** 28 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5q98-285h-hg3j

## What is CVE-2006-7222?

CVE-2006-7222 is a medium-severity memory corruption vulnerability in n/a, published on 28 Aug 2007. 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

Buffer overflow in the CFLICStream::_deltachunk function in FLICSource.cpp in Media Player Classic (MPC) 6.4.9.0 allows user-assisted remote attackers to execute arbitrary code via a crafted FLI file.

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

## Which versions are affected by CVE-2006-7222?

It affects 1 product.


Products: Guliverkli Media Player Classic.

## How do I fix CVE-2006-7222?

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

## Is CVE-2006-7222 being exploited?

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

Public exploit code:

- Media Player Classic 6.4.9 - FLI File Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4939](https://insights.sbomify.com/CVE-2007-4939/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-4940](https://insights.sbomify.com/CVE-2007-4940/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7222 and fix it if it is affected.

What it is: CVE-2006-7222 is a medium-severity memory corruption vulnerability in n/a, published on 28 Aug 2007. 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-2006-7222 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-2006-7222/ (Markdown: https://insights.sbomify.com/CVE-2006-7222/index.md)
```

## Sources

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

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