# CVE-2019-17109: koji hub allows arbitrary upload destinations

> Remote attackers can exploit directory traversal in Koji to achieve privilege escalation, requiring immediate upgrades.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 9 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7498-c9fm-g64p, MGASA-2021-0147, PYSEC-2019-183, UBUNTU-CVE-2019-17109

## What is CVE-2019-17109?

CVE-2019-17109 is a medium-severity path traversal vulnerability in n/a, published on 9 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Koji through 1.18.0 allows remote Directory Traversal, with resultant Privilege Escalation.

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

## Which versions are affected by CVE-2019-17109?

11 open source packages ship an affected version, including koji. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `koji` | PyPI | All versions | 1.19.0 |
| `koji` | PyPI | From 1.14.0 | 1.14.3 |
| `koji` | PyPI | From 1.14.0 | 1.14.3 |
| `koji` | PyPI | From 1.15.0 | 1.15.3 |
| `koji` | PyPI | From 1.15.0 | 1.15.3 |
| `koji` | PyPI | From 1.16.0 | 1.16.3 |
| `koji` | PyPI | From 1.16.0 | 1.16.3 |
| `koji` | PyPI | From 1.17.0 | 1.17.1 |
| `koji` | PyPI | From 1.17.0 | 1.17.1 |
| `koji` | PyPI | From 1.18.0 | 1.18.1 |
| `koji` | PyPI | From 1.18.0 | 1.18.1 |

Products: Koji Project Koji.

## How do I fix CVE-2019-17109?

Upgrade koji to a fixed version for your release line: 1.19.0, 1.14.3, 1.15.3 or 1.16.3.

## Is CVE-2019-17109 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1002150](https://insights.sbomify.com/CVE-2018-1002150/): Koji hub call does not perform correct access checks (critical 9.1)
- [CVE-2017-1002153](https://insights.sbomify.com/CVE-2017-1002153/): Koji blacklisted paths workaround (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17109 and fix it if it is affected.

What it is: CVE-2019-17109 is a medium-severity path traversal vulnerability in n/a, published on 9 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17109 in the wild and no public exploit code.

Affected packages and fixed versions:
- koji (PyPI): affected all versions; fixed in 1.19.0
- koji (PyPI): affected from 1.14.0; fixed in 1.14.3
- koji (PyPI): affected from 1.14.0; fixed in 1.14.3
- koji (PyPI): affected from 1.15.0; fixed in 1.15.3
- koji (PyPI): affected from 1.15.0; fixed in 1.15.3
- koji (PyPI): affected from 1.16.0; fixed in 1.16.3
- koji (PyPI): affected from 1.16.0; fixed in 1.16.3
- koji (PyPI): affected from 1.17.0; fixed in 1.17.1
- koji (PyPI): affected from 1.17.0; fixed in 1.17.1
- koji (PyPI): affected from 1.18.0; fixed in 1.18.1
- koji (PyPI): affected from 1.18.0; fixed in 1.18.1

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-2019-17109/ (Markdown: https://insights.sbomify.com/CVE-2019-17109/index.md)
```

## Sources

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

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