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

> A heap overwrite in libvorbis allows attackers to cause denial of service or execute arbitrary code via malicious audio files.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** Yes
- **Published:** 26 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-3106, GHSA-g2r6-v9mj-qx9w

## What is CVE-2007-3106?

CVE-2007-3106 is a medium-severity memory corruption vulnerability in n/a, published on 26 Jul 2007. 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

lib/info.c in libvorbis 1.1.2, and possibly other versions before 1.2.0, allows context-dependent attackers to cause a denial of service and possibly execute arbitrary code via invalid (1) blocksize_0 and (2) blocksize_1 values, which trigger a "heap overwrite" in the _01inverse function in res0.c.  NOTE: this issue has been RECAST so that CVE-2007-4029 handles additional vectors.

Weakness: CWE-399

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

It affects 1 product.


Products: Libvorbis Libvorbis.

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

Upgrade to a fixed version.

## Is CVE-2007-3106 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4029](https://insights.sbomify.com/CVE-2007-4029/): Denial of service in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3106 is a medium-severity memory corruption vulnerability in n/a, published on 26 Jul 2007. 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-3106 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-3106/ (Markdown: https://insights.sbomify.com/CVE-2007-3106/index.md)
```

## Sources

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

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