CVE-2018-1002150 — koji
CRITICALCVE-2018-1002150 is a critical-severity (CVSS 9.1) CWE-732 vulnerability in koji. A fix is available for koji — see the affected versions and patch details below.
Koji hub call does not perform correct access checks
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2018-1002150 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
koji🐍koji🐍koji🐍kojiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | koji | ≥ 1.15&&< 1.15.1 | 1.15.1pip install --upgrade 'koji==1.15.1' |
| 🐍PyPI | koji | ≥ 1.14&&< 1.14.1 | 1.14.1pip install --upgrade 'koji==1.14.1' |
| 🐍PyPI | koji | ≥ 1.13&&< 1.13.1 | 1.13.1pip install --upgrade 'koji==1.13.1' |
| 🐍PyPI | koji | ≥ 1.12&&< 1.12.1 | 1.12.1pip install --upgrade 'koji==1.12.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for koji, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update koji to 1.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1002150 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2018-1002150 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2018-1002150. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2018-1002150 in your dependencies?
O3 Security finds CVE-2018-1002150 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.