# CVE-2018-1002150: Koji hub call does not perform correct access checks

> Koji build system allows arbitrary filesystem read/write access due to incorrect access control, requiring an upgrade to patched versions.

- **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:** 4 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6mww-xvh7-fq4f, PYSEC-2018-86, UBUNTU-CVE-2018-1002150

## What is CVE-2018-1002150?

CVE-2018-1002150 is a critical missing authorization vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Koji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrary filesystem read/write access. This vulnerability has been fixed in versions 1.12.1, 1.13.1, 1.14.1 and 1.15.1.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-1002150?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `koji` | PyPI | All versions | 1.15.1 |
| `koji` | PyPI | From 1.12 | 1.12.1 |
| `koji` | PyPI | From 1.12 | 1.12.1 |
| `koji` | PyPI | From 1.13 | 1.13.1 |
| `koji` | PyPI | From 1.13 | 1.13.1 |
| `koji` | PyPI | From 1.14 | 1.14.1 |
| `koji` | PyPI | From 1.14 | 1.14.1 |
| `koji` | PyPI | From 1.15 | 1.15.1 |
| `koji` | PyPI | From 1.15 | 1.15.1 |

Products: Koji Project Koji.

## How do I fix CVE-2018-1002150?

Upgrade koji to a fixed version for your release line: 1.15.1, 1.12.1, 1.13.1 or 1.14.1.

## Is CVE-2018-1002150 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-1002153](https://insights.sbomify.com/CVE-2017-1002153/): Koji blacklisted paths workaround (high 7.5)
- [CVE-2019-17109](https://insights.sbomify.com/CVE-2019-17109/): koji hub allows arbitrary upload destinations (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1002150 and fix it if it is affected.

What it is: CVE-2018-1002150 is a critical missing authorization vulnerability in n/a, published on 4 Apr 2018. 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-2018-1002150 in the wild and no public exploit code.

Affected packages and fixed versions:
- koji (PyPI): affected all versions; fixed in 1.15.1
- koji (PyPI): affected from 1.12; fixed in 1.12.1
- koji (PyPI): affected from 1.12; fixed in 1.12.1
- koji (PyPI): affected from 1.13; fixed in 1.13.1
- koji (PyPI): affected from 1.13; fixed in 1.13.1
- koji (PyPI): affected from 1.14; fixed in 1.14.1
- koji (PyPI): affected from 1.14; fixed in 1.14.1
- koji (PyPI): affected from 1.15; fixed in 1.15.1
- koji (PyPI): affected from 1.15; fixed in 1.15.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-2018-1002150/ (Markdown: https://insights.sbomify.com/CVE-2018-1002150/index.md)
```

## Sources

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

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