# CVE-2005-2718: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted PCM audio data in MPlayer, requiring user interaction to open a malicious file.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 29 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c769-3v9w-jrgf

## What is CVE-2005-2718?

CVE-2005-2718 is a high-severity memory corruption vulnerability in n/a, published on 29 Aug 2005. 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 ad_pcm.c in MPlayer 1.0pre7 and earlier allows remote attackers to execute arbitrary code via crafted PCM audio data, as demonstrated using a video file with an audio header containing a large value in a stream format (strf) chunk.

## Which versions are affected by CVE-2005-2718?

It affects 1 product.


Products: Mplayer Mplayer.

## How do I fix CVE-2005-2718?

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

## Is CVE-2005-2718 being exploited?

There is no known exploitation of CVE-2005-2718 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-1311](https://insights.sbomify.com/CVE-2004-1311/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2718 and fix it if it is affected.

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

## Sources

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

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