# CVE-2008-5072: Denial of service in n/a

> Remote attackers can crash the K-Lite Mega Codec Pack application by tricking users into opening a malformed FLV file.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 14 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-66qm-qp62-322f

## What is CVE-2008-5072?

CVE-2008-5072 is a medium-severity denial of service vulnerability in n/a, published on 14 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

vsfilter.dll in K-Lite Mega Codec Pack 3.5.7.0 allows remote attackers to cause a denial of service (application crash) via a malformed FLV file.

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

It affects 1 product.


Products: K-Lite Mega Codec Pack.

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

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

## Is CVE-2008-5072 being exploited?

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

Public exploit code:

- K-Lite Mega Codec Pack 3.5.7.0 - Local Windows Explorer Denial of Service (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5072 is a medium-severity denial of service vulnerability in n/a, published on 14 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5072 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-5072/ (Markdown: https://insights.sbomify.com/CVE-2008-5072/index.md)
```

## Sources

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

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