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

> Attackers can cause a denial of service in applications using libvorbis by providing malicious audio files with invalid mapping or blocksize values.

- **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-4029, GHSA-f885-7gr5-w3p4

## What is CVE-2007-4029?

CVE-2007-4029 is a medium-severity denial of service 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

libvorbis 1.1.2, and possibly other versions before 1.2.0, allows context-dependent attackers to cause a denial of service via (1) an invalid mapping type, which triggers an out-of-bounds read in the vorbis_info_clear function in info.c, and (2) invalid blocksize values that trigger a segmentation fault in the read function in block.c.

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

It affects 1 product.


Products: Libvorbis Libvorbis.

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

Upgrade to a fixed version.

## Is CVE-2007-4029 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3106](https://insights.sbomify.com/CVE-2007-3106/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4029 is a medium-severity denial of service 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-4029 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-4029/ (Markdown: https://insights.sbomify.com/CVE-2007-4029/index.md)
```

## Sources

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

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