# CVE-2004-0372: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks in xine bug report scripts, requiring user interaction to generate the report.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0372, DSA-477, GHSA-gcqg-g524-q8fj

## What is CVE-2004-0372?

CVE-2004-0372 is a low-severity path traversal vulnerability in n/a, published on 27 Mar 2004. 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

xine allows local users to overwrite arbitrary files via a symlink attack on a bug report email that is generated by the (1) xine-bugreport or (2) xine-check scripts.

## Which versions are affected by CVE-2004-0372?

It affects 1 product.


Products: Xine Xine.

## How do I fix CVE-2004-0372?

Apply the vendor's patch.

## Is CVE-2004-0372 being exploited?

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

## 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-2004-0372 and fix it if it is affected.

What it is: CVE-2004-0372 is a low-severity path traversal vulnerability in n/a, published on 27 Mar 2004. 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-2004-0372 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-2004-0372/ (Markdown: https://insights.sbomify.com/CVE-2004-0372/index.md)
```

## Sources

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

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