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

> Remote attackers can write files outside the module path in rsync daemons configured without chroot, requiring an upgrade to fix.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Apr 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0426, DSA-499, GHSA-8hxr-8xgg-w97m, RHSA-2004:192

## What is CVE-2004-0426?

CVE-2004-0426 is a medium-severity path traversal vulnerability in n/a, published on 30 Apr 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

rsync before 2.6.1 does not properly sanitize paths when running a read/write daemon without using chroot, which allows remote attackers to write files outside of the module's path.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsync` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5.7-4.3E |
| `rsync-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5.7-4.3E |
| `rsync` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5.7-4.3E |
| `rsync-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5.7-4.3E |
| `rsync` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5.7-4.3E |
| `rsync-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5.7-4.3E |
| `rsync` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5.7-4.3E |
| `rsync-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5.7-4.3E |

Products: Andrew Tridgell Rsync.

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

Upgrade to a fixed version.

## Is CVE-2004-0426 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0048](https://insights.sbomify.com/CVE-2002-0048/): Integer overflow in n/a (critical 10.0)
- [CVE-2006-2083](https://insights.sbomify.com/CVE-2006-2083/): Integer overflow in n/a (high 7.5)
- [CVE-2003-0962](https://insights.sbomify.com/CVE-2003-0962/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0792](https://insights.sbomify.com/CVE-2004-0792/): Path traversal in n/a (medium 6.4)
- [CVE-1999-0473](https://insights.sbomify.com/CVE-1999-0473/): Misconfiguration in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0426 is a medium-severity path traversal vulnerability in n/a, published on 30 Apr 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0426 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-0426/ (Markdown: https://insights.sbomify.com/CVE-2004-0426/index.md)
```

## Sources

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

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