# CVE-2007-6731: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a malicious OXM file due to a buffer overflow in Extended Module Player.

- **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:** 13 Sep 2009
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2007-6731, GHSA-5xjw-36fw-5xm4

## What is CVE-2007-6731?

CVE-2007-6731 is a critical memory corruption vulnerability in n/a, published on 13 Sep 2009. 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

Extended Module Player (XMP) 2.5.1 and earlier allow remote attackers to execute arbitrary code via an OXM file with a negative value, which bypasses a check in (1) test_oxm and (2) decrunch_oxm functions in misc/oxm.c, leading to a buffer overflow.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2007-6731?

It affects 1 product.


Products: Claudio Matsuoka Extended Module Player.

## How do I fix CVE-2007-6731?

Upgrade to a fixed version.

## Is CVE-2007-6731 being exploited?

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

Public exploit code:

- Extended Module Player (xmp) 2.5.1 - 'oxm.c' / 'dtt_load.c' Multiple Local Buffer Overflow Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6732](https://insights.sbomify.com/CVE-2007-6732/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6731 and fix it if it is affected.

What it is: CVE-2007-6731 is a critical memory corruption vulnerability in n/a, published on 13 Sep 2009. 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-2007-6731 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-2007-6731/ (Markdown: https://insights.sbomify.com/CVE-2007-6731/index.md)
```

## Sources

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

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