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

CVE-2018-1002150 · Severity: low · CVSS 3 · Published 2018-04-04

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.

Technologies: koji (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2018-1002150 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-1002150 being exploited in the wild.
How severe is CVE-2018-1002150?
Low severity, with a CVSS score of 3, published 4 April 2018.
Which products and versions are affected?
koji (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.1, ECOSYSTEM:introduced=1.15,fixed=1.15.1.
Is there a fix for CVE-2018-1002150?
Yes. koji (PyPI): upgrade to 1.15.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1002150?
Check whether you run koji (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • koji (PyPI): upgrade to 1.15.1 or later
    pip install "koji>=1.15.1"

Affected products

  • koji (PyPI) ECOSYSTEM:introduced=0,fixed=1.15.1, ECOSYSTEM:introduced=1.15,fixed=1.15.1

Identifiers

  • CVE-2018-1002150
  • GHSA-6mww-xvh7-fq4f
  • PYSEC-2018-86

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.