# CVE-2007-0254: Other in n/a

> A format string vulnerability in xine-ui allows attackers to execute arbitrary code, requiring user interaction to trigger the error window.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 16 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-0254, GHSA-862g-ghxh-g8f8

## What is CVE-2007-0254?

CVE-2007-0254 is a critical vulnerability in n/a, published on 16 Jan 2007. 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

Format string vulnerability in the errors_create_window function in errors.c in xine-ui allows attackers to execute arbitrary code via unknown vectors.

## Which versions are affected by CVE-2007-0254?

It affects 1 product.


Products: Xine Xine-Ui.

## How do I fix CVE-2007-0254?

Upgrade to a fixed version.

## Is CVE-2007-0254 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0254 and fix it if it is affected.

What it is: CVE-2007-0254 is a critical vulnerability in n/a, published on 16 Jan 2007. 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: There is no known exploitation of CVE-2007-0254 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-2007-0254/ (Markdown: https://insights.sbomify.com/CVE-2007-0254/index.md)
```

## Sources

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

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