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

> Attackers can cause denial of service in xine via format string vulnerabilities in MP3 filenames provided on the command line.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2230, DSA-1093-1, GHSA-rm7g-xfrp-h3v4

## What is CVE-2006-2230?

CVE-2006-2230 is a medium-severity memory corruption vulnerability in n/a, published on 5 May 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Multiple format string vulnerabilities in xiTK (xitk/main.c) in xine 0.99.4 might allow attackers to cause a denial of service via format string specifiers in an MP3 filename specified on the command line. NOTE: this is a different vulnerability than CVE-2006-1905.  In addition, if the only attack vectors involve a user-assisted, local command line argument of a non-setuid program, this issue might not be a vulnerability.

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

It affects 1 product.


Products: Xine Xine.

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

Apply the vendor's patch.

## Is CVE-2006-2230 being exploited?

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

Public exploit code:

- Xine 0.99.x - Filename Handling Remote Format String (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5237](https://insights.sbomify.com/CVE-2008-5237/): Integer overflow in n/a (critical 10.0)
- [CVE-2008-5235](https://insights.sbomify.com/CVE-2008-5235/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-5236](https://insights.sbomify.com/CVE-2008-5236/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0255](https://insights.sbomify.com/CVE-2007-0255/): Memory corruption in n/a (critical 9.3)
- [CVE-2006-1905](https://insights.sbomify.com/CVE-2006-1905/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2230 is a medium-severity memory corruption vulnerability in n/a, published on 5 May 2006. It can only be exploited from the same machine or local network, 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-2230 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-2230/ (Markdown: https://insights.sbomify.com/CVE-2006-2230/index.md)
```

## Sources

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

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