# CVE-2007-6720: Denial of service in n/a

> An attacker can cause a denial of service in applications using libmikmod by tricking a user into loading multiple MOD files with different channel counts.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6720, GHSA-ggqw-hm64-w646

## What is CVE-2007-6720?

CVE-2007-6720 is a medium-severity denial of service vulnerability in n/a, published on 20 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

libmikmod 3.1.9 through 3.2.0, as used by MikMod, SDL-mixer, and possibly other products, relies on the channel count of the last loaded song, rather than the currently playing song, for certain playback calculations, which allows user-assisted attackers to cause a denial of service (application crash) by loading multiple songs (aka MOD files) with different numbers of channels.

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

It affects 1 product.


Products: Igno Saitz Libmikmod.

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

Upgrade to a fixed version.

## Is CVE-2007-6720 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0179](https://insights.sbomify.com/CVE-2009-0179/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6720 is a medium-severity denial of service vulnerability in n/a, published on 20 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-6720 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-6720/ (Markdown: https://insights.sbomify.com/CVE-2007-6720/index.md)
```

## Sources

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

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