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

> Local attackers can execute arbitrary code via a buffer overflow in Avahi, potentially escalating privileges.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2289, GHSA-wcpr-m747-77wq

## What is CVE-2006-2289?

CVE-2006-2289 is a low-severity memory corruption vulnerability in n/a, published on 9 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in avahi-core in Avahi before 0.6.10 allows local users to execute arbitrary code via unknown vectors.

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

It affects 1 product.


Products: Avahi Avahi.

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

Upgrade to a fixed version.

## Is CVE-2006-2289 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6519](https://insights.sbomify.com/CVE-2017-6519/): Denial of service in n/a (critical 9.1)
- [CVE-2021-26720](https://insights.sbomify.com/CVE-2021-26720/): Path traversal in n/a (high 7.8)
- [CVE-2026-24401](https://insights.sbomify.com/CVE-2026-24401/): Avahi has Uncontrolled Recursion in lookup_handle_cname function (medium 6.5)
- [CVE-2025-68468](https://insights.sbomify.com/CVE-2025-68468/): Avahi has a reachable assertion in lookup_multicast_callback (medium 6.5)
- [CVE-2025-68471](https://insights.sbomify.com/CVE-2025-68471/): Avahi has a reachable assertion in lookup_start (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2289 is a low-severity memory corruption vulnerability in n/a, published on 9 May 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2289 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-2289/ (Markdown: https://insights.sbomify.com/CVE-2006-2289/index.md)
```

## Sources

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

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