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

> Remote attackers can cause denial of service or execute code via buffer overflows in TunePimp library when processing malicious metadata.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 14 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2006-3466, DSA-1135-1, GHSA-8fvc-4frw-3hwh

## What is CVE-2006-3600?

CVE-2006-3600 is a medium-severity memory corruption vulnerability in n/a, published on 14 Jul 2006. 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 stack-based buffer overflows in the LookupTRM::lookup function in libtunepimp (TunePimp) 0.4.2 allow remote user-assisted attackers to cause a denial of service (application crash) and possibly execute code via a long (1) Album release date (MBE_ReleaseGetDate), (2) data, or (3) error strings.

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

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

It affects 1 product.


Products: Libtunepimp Libtunepimp.

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

Upgrade to a fixed version.

## Is CVE-2006-3600 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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