# CVE-2017-8805: Path traversal in Debian ftpsync before 20171017

> Remote attackers can perform directory traversal via a crafted upstream mirror because Debian ftpsync fails to use the rsync --safe-links option.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-8805, GHSA-f9qc-p869-hxxw

## What is CVE-2017-8805?

CVE-2017-8805 is a critical path traversal vulnerability in Debian ftpsync before 20171017, published on 17 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Debian ftpsync before 20171017 does not use the rsync --safe-links option, which allows remote attackers to conduct directory traversal attacks via a crafted upstream mirror.

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

## Which versions are affected by CVE-2017-8805?

It affects 1 product.


Products: Debian Ftpsync.

## How do I fix CVE-2017-8805?

Upgrade to a fixed version.

## Is CVE-2017-8805 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8805 and fix it if it is affected.

What it is: CVE-2017-8805 is a critical path traversal vulnerability in Debian ftpsync before 20171017, published on 17 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8805 in the wild and no public exploit code.

Affected product: Debian ftpsync before 20171017. 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-2017-8805/ (Markdown: https://insights.sbomify.com/CVE-2017-8805/index.md)
```

## Sources

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

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