CVE-2018-1002150 json
Koji hub call does not perform correct access checks
published 8y ago modified 4mo ago also GHSA-6mww-xvh7-fq4f , PYSEC-2018-86 , EUVD-2018-0085
- cvss
- 9.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi koji 1.12.1, 1.13.1, 1.14.1, 1.15.1
Is CVE-2018-1002150 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | koji | >=1.15, <1.15.1 >=1.14, <1.14.1 >=1.13, <1.13.1 >=1.12, <1.12.1 <1.15.1 |
1.15.1 1.14.1 1.13.1 1.12.1 |
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
docs.pagure.org
/koji/CVE-2018-1002150/
mitigation, third-party-advisory, web
-
pagure.io
/koji/issue/850
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-1002150
advisory
-
docs.pagure.org
/koji/CVE-2018-1002150
web
-
github.com
/advisories/GHSA-6mww-xvh7-fq4f
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/koji/PYSEC-2018-86.yaml
web
-
pagure.io
/koji
package
-
pagure.io
/koji/c/ab1ade7
web
Sources
- CVE List CVE-2018-1002150
- GitHub Advisory GHSA-6mww-xvh7-fq4f
- NVD CVE-2018-1002150
- OSV PYSEC-2018-86
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.