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

> Remote attackers can cause denial of service or potentially execute code via buffer overflows in AlsaPlayer when processing malicious web or CDDB responses.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 11 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4089, DSA-1179-1, GHSA-7hmv-cv83-p85q

## What is CVE-2006-4089?

CVE-2006-4089 is a medium-severity memory corruption vulnerability in n/a, published on 11 Aug 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 buffer overflows in Andy Lo-A-Foe AlsaPlayer 0.99.76 and earlier allow remote attackers to cause a denial of service (application crash), or have other unknown impact, via (1) a long Location field sent by a web server, which triggers an overflow in the reconnect function in reader/http/http.c; (2) a long URL sent by a web server when AlsaPlayer is seeking a media file for the playlist, which triggers overflows in new_list_item and CbUpdated in interface/gtk/PlaylistWindow.cpp; and (3) a long response sent by a CDDB server, which triggers an overflow in cddb_lookup in input/ccda/cdda_engine.c.

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

It affects 1 product.


Products: Andy Lo-a-Foe Alsaplayer.

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

Upgrade to a fixed version.

## Is CVE-2006-4089 being exploited?

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

Public exploit code:

- AlsaPlayer 0.99.x - Multiple Buffer Overflow Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4089 is a medium-severity memory corruption vulnerability in n/a, published on 11 Aug 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4089 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-4089/ (Markdown: https://insights.sbomify.com/CVE-2006-4089/index.md)
```

## Sources

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

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