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

koji Updated 02 Oct 2025

Summary

12/07/2018
Yes i
Critical
9.1

CVE-2018-1002150: Koji hub call does not perform correct access checks. Affects koji across 4 version ranges.

>= 1.12, < 1.12.1 >= 1.13, < 1.13.1 >= 1.14, < 1.14.1 >= 1.15, < 1.15.1

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Koji is an open-source build system that facilitates the creation and management of software packages. It is widely used in the Python ecosystem. This vulnerability affects Koji versions 1.12, 1.13, 1.14, and 1.15. Koji's hub call does not properly perform access checks, leading to arbitrary filesystem read/write access. This vulnerability has a CVSS score of 9.1 (Critical).

Vulnerability Detail

The vulnerability in Koji allows an attacker to gain unauthorized access to the filesystem, potentially leading to the compromise of sensitive data or the execution of arbitrary code. By exploiting this vulnerability, an attacker can read or modify files on the system, bypassing intended access restrictions. This can have severe consequences, including unauthorized data disclosure, privilege escalation, or even a complete system compromise.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 1.12, < 1.12.1 1.12.1
    pip install --upgrade "koji==1.12.1"
  • >= 1.13, < 1.13.1 1.13.1
    pip install --upgrade "koji==1.13.1"
  • >= 1.14, < 1.14.1 1.14.1
    pip install --upgrade "koji==1.14.1"
  • >= 1.15, < 1.15.1 1.15.1
    pip install --upgrade "koji==1.15.1"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the patched versions as soon as possible to mitigate the risk of exploitation.

Conclusion

The vulnerability in Koji's access control can have severe consequences, including unauthorized access to the filesystem and potential compromise of sensitive data. It is crucial to upgrade to the patched versions (1.12.1, 1.13.1, 1.14.1, or 1.15.1) to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for koji →

Share this vulnerability

FAQ

Koji is an open-source build system used for creating and managing software packages.

Koji versions 1.12, 1.13, 1.14, and 1.15 are affected.

The vulnerability allows unauthorized filesystem read/write access, which can lead to data disclosure, privilege escalation, or system compromise.

Upgrade to the patched versions of Koji: 1.12.1, 1.13.1, 1.14.1, or 1.15.1.

No, there is no known workaround. Upgrading to the patched versions is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for koji.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 1.12, < 1.12.1 1.12.1
    pip install --upgrade "koji==1.12.1"
  • >= 1.13, < 1.13.1 1.13.1
    pip install --upgrade "koji==1.13.1"
  • >= 1.14, < 1.14.1 1.14.1
    pip install --upgrade "koji==1.14.1"
  • >= 1.15, < 1.15.1 1.15.1
    pip install --upgrade "koji==1.15.1"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback