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

> A malicious SSH server can exploit a directory traversal flaw in the OpenSSH client to overwrite arbitrary files on the connecting user's system.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0175, GHSA-384q-pv6w-p8vv, RHSA-2005:074, RHSA-2005:106, RHSA-2005:165

## What is CVE-2004-0175?

CVE-2004-0175 is a medium-severity path traversal vulnerability in OpenSSH, published on 3 Jun 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in scp for OpenSSH before 3.4p1 allows remote malicious servers to overwrite arbitrary files.  NOTE: this may be a rediscovery of CVE-2000-0992.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssh` | Red Hat:enterprise_linux:3::as | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass` | Red Hat:enterprise_linux:3::as | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass-gnome` | Red Hat:enterprise_linux:3::as | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-clients` | Red Hat:enterprise_linux:3::as | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-server` | Red Hat:enterprise_linux:3::as | All versions | 0:3.6.1p2-33.30.4 |
| `rsh` | Red Hat:enterprise_linux:3::as | All versions | 0:0.17-17.6 |
| `rsh-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:0.17-17.6 |
| `rsh-server` | Red Hat:enterprise_linux:3::as | All versions | 0:0.17-17.6 |
| `openssh` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass-gnome` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-clients` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-server` | Red Hat:enterprise_linux:3::desktop | All versions | 0:3.6.1p2-33.30.4 |
| `rsh` | Red Hat:enterprise_linux:3::desktop | All versions | 0:0.17-17.6 |
| `rsh-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:0.17-17.6 |
| `rsh-server` | Red Hat:enterprise_linux:3::desktop | All versions | 0:0.17-17.6 |
| `openssh` | Red Hat:enterprise_linux:3::es | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass` | Red Hat:enterprise_linux:3::es | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass-gnome` | Red Hat:enterprise_linux:3::es | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-clients` | Red Hat:enterprise_linux:3::es | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-server` | Red Hat:enterprise_linux:3::es | All versions | 0:3.6.1p2-33.30.4 |
| `rsh` | Red Hat:enterprise_linux:3::es | All versions | 0:0.17-17.6 |
| `rsh-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:0.17-17.6 |
| `rsh-server` | Red Hat:enterprise_linux:3::es | All versions | 0:0.17-17.6 |
| `openssh` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-askpass-gnome` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-clients` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.6.1p2-33.30.4 |
| `openssh-server` | Red Hat:enterprise_linux:3::ws | All versions | 0:3.6.1p2-33.30.4 |
| `rsh` | Red Hat:enterprise_linux:3::ws | All versions | 0:0.17-17.6 |
| `rsh-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:0.17-17.6 |
| `rsh-server` | Red Hat:enterprise_linux:3::ws | All versions | 0:0.17-17.6 |
| `rsh` | Red Hat:enterprise_linux:4::as | All versions | 0:0.17-25.3 |
| `rsh-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.17-25.3 |
| `rsh-server` | Red Hat:enterprise_linux:4::as | All versions | 0:0.17-25.3 |
| `rsh` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.17-25.3 |

Products: OpenSSH.

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

Upgrade to a fixed version.

## Is CVE-2004-0175 being exploited?

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

## Other vulnerabilities in OpenSSH

- [CVE-2003-0786](https://insights.sbomify.com/CVE-2003-0786/): Auth bypass in n/a (critical 10.0)
- [CVE-2003-0693](https://insights.sbomify.com/CVE-2003-0693/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0640](https://insights.sbomify.com/CVE-2002-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0144](https://insights.sbomify.com/CVE-2001-0144/): Integer overflow in n/a (critical 10.0)
- [CVE-2000-0999](https://insights.sbomify.com/CVE-2000-0999/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0175 is a medium-severity path traversal vulnerability in OpenSSH, published on 3 Jun 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-0175 in the wild and no public exploit code.

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

## Sources

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

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