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

> Local attackers can overwrite arbitrary files via symlink attacks on temporary files in sysstat scripts, potentially compromising system integrity.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 16 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0107, GHSA-3hhr-4c49-xc95

## What is CVE-2004-0107?

CVE-2004-0107 is a medium-severity path traversal vulnerability in Sgi Propack, published on 16 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The (1) post and (2) trigger scripts in sysstat 4.0.7 and earlier allow local users to overwrite arbitrary files via symlink attacks on temporary files, a different vulnerability than CVE-2004-0108.

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

It affects 3 products.


Products: Redhat Sysstat, Sgi Propack, Sysstat Sysstat.

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

Upgrade to a fixed version.

## Is CVE-2004-0107 being exploited?

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

## Other vulnerabilities in Sgi Propack

- [CVE-2004-0108](https://insights.sbomify.com/CVE-2004-0108/): Path traversal in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0107 and fix it if it is affected.

What it is: CVE-2004-0107 is a medium-severity path traversal vulnerability in Sgi Propack, published on 16 Mar 2004. 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-2004-0107 in the wild and no public exploit code.

Affected product: Sgi Propack. 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-0107/ (Markdown: https://insights.sbomify.com/CVE-2004-0107/index.md)
```

## Sources

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

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