# CVE-2004-1311: Integer overflow in n/a

> Remote attackers can cause a crash or execute arbitrary code via a malicious Real RTSP file exploiting an integer overflow 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-1311, GHSA-gxf7-qxj8-45vp

## What is CVE-2004-1311?

CVE-2004-1311 is a critical 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

Integer overflow in the real_setup_and_get_header function in real.c for Unix MPlayer 1.0pre5 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a Real RTSP streaming media file with a -1 content-length field, which leads to a heap-based buffer overflow.

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

It affects 1 product.


Products: Mplayer Mplayer.

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

Upgrade to a fixed version.

## Is CVE-2004-1311 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5616](https://insights.sbomify.com/CVE-2008-5616/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-1558](https://insights.sbomify.com/CVE-2008-1558/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-1285](https://insights.sbomify.com/CVE-2004-1285/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1310](https://insights.sbomify.com/CVE-2004-1310/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0659](https://insights.sbomify.com/CVE-2004-0659/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1311 is a critical 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-1311 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-1311/ (Markdown: https://insights.sbomify.com/CVE-2004-1311/index.md)
```

## Sources

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

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