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

> Remote attackers can execute arbitrary code via buffer overflows in the dtt_load function when processing malicious module files.

- **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:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2007-6732, GHSA-3hmr-jrgj-vchc

## What is CVE-2007-6732?

CVE-2007-6732 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

Multiple buffer overflows in the dtt_load function in loaders/dtt_load.c Extended Module Player (XMP) 2.5.1 and earlier allow remote attackers to execute arbitrary code via unspecified vectors related to an untrusted length value and the (1) pofs and (2) plen arrays.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Claudio Matsuoka Extended Module Player.

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

Upgrade to a fixed version.

## Is CVE-2007-6732 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6732 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: There is no known exploitation of CVE-2007-6732 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-2007-6732/ (Markdown: https://insights.sbomify.com/CVE-2007-6732/index.md)
```

## Sources

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

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