# CVE-2004-1309: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious BMP file in MPlayer.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 22 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1309, GHSA-xxfg-v7qr-vxwh

## What is CVE-2004-1309?

CVE-2004-1309 is a critical memory corruption vulnerability in n/a, published on 22 Dec 2004. 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

Heap-based buffer overflow in the demux_open_bmp function in demux_bmp.c for Unix MPlayer 1.0pre5 allows remote attackers to execute arbitrary code via a bitmap (BMP) file containing a large biClrUsed field.

## Which versions are affected by CVE-2004-1309?

It affects 1 product.


Products: Mplayer Unix Mplayer.

## How do I fix CVE-2004-1309?

Upgrade to a fixed version.

## Is CVE-2004-1309 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1309 and fix it if it is affected.

What it is: CVE-2004-1309 is a critical memory corruption vulnerability in n/a, published on 22 Dec 2004. 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-2004-1309 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-2004-1309/ (Markdown: https://insights.sbomify.com/CVE-2004-1309/index.md)
```

## Sources

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

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