# CVE-2006-4197: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via buffer overflows in the MusicBrainz client library.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 17 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1162, GHSA-7fj4-5cwr-pcgr

## What is CVE-2006-4197?

CVE-2006-4197 is a high-severity memory corruption vulnerability in n/a, published on 17 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in libmusicbrainz (aka mb_client or MusicBrainz Client Library) 2.1.2 and earlier, and SVN 8406 and earlier, allow remote attackers to cause a denial of service (crash) or execute arbitrary code via (1) a long Location header by the HTTP server, which triggers an overflow in the MBHttp::Download function in lib/http.cpp; and (2) a long URL in RDF data, as demonstrated by a URL in an rdf:resource field in an RDF XML document, which triggers overflows in many functions in lib/rdfparse.c.

## Which versions are affected by CVE-2006-4197?

It affects 2 products.


Products: Musicbrainz Libmusicbrainz, Musicbrainz Libmusicbrainz Svn.

## How do I fix CVE-2006-4197?

Upgrade to a fixed version.

## Is CVE-2006-4197 being exploited?

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

Public exploit code:

- Libmusicbrainz 2.0.2/2.1.x - Multiple Buffer Overflow Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4197 and fix it if it is affected.

What it is: CVE-2006-4197 is a high-severity memory corruption vulnerability in n/a, published on 17 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4197 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-2006-4197/ (Markdown: https://insights.sbomify.com/CVE-2006-4197/index.md)
```

## Sources

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

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