# CVE-2017-9031: Path traversal in n/a

> An attacker can exploit a directory traversal flaw in the Deluge WebUI to read arbitrary files from the server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9031, DLA-943-1, GHSA-fffq-gprj-v9cm, MGASA-2017-0449, UBUNTU-CVE-2017-9031, openSUSE-SU-2024:10713-1

## What is CVE-2017-9031?

CVE-2017-9031 is a critical path traversal vulnerability in n/a, published on 17 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WebUI component in Deluge before 1.3.15 contains a directory traversal vulnerability involving a request in which the name of the render file is not associated with any template file.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `deluge` | openSUSE:Tumbleweed | All versions | 2.0.3-4.7 |

Products: Deluge-Torrent Deluge.

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

Upgrade to a fixed version.

## Is CVE-2017-9031 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-25585](https://insights.sbomify.com/CVE-2019-25585/): Deluge 1.3.15 Denial of Service via Webseeds Field (medium 6.9)
- [CVE-2019-25586](https://insights.sbomify.com/CVE-2019-25586/): Deluge 1.3.15 Denial of Service via URL Field (medium 6.9)
- [CVE-2021-3427](https://insights.sbomify.com/CVE-2021-3427/): Deluge Web-UI vulnerable to XSS through a crafted torrent file (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9031 is a critical path traversal vulnerability in n/a, published on 17 May 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-9031 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-2017-9031/ (Markdown: https://insights.sbomify.com/CVE-2017-9031/index.md)
```

## Sources

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

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