CVE-2017-1002153: Koji 1.13.0 does not properly validate SCM paths, allowing an attacker to work around blacklisted paths for bu

This month

HIGH 7.5REMOTEDOWNGRADE

CVE-2017-1002153 is a high-severity flaw (CVSS 7.5) affecting koji. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Koji 1.13.0 does not properly validate SCM paths, allowing an attacker to work around blacklisted paths for build submission.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 33%)
CISA exploited list	No
Weakness	CWE-20
Published	2017-10-06
Last modified	2026-06-17

Publisher (CNA): Fedora Project · Vendor: koji project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-10-06 17:29 UTCPublished CVE record published
2026-06-17 00:59 UTCUpdated Record last modified

koji project koji DOWNGRADE

Affected: 1.13.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.13.0

1. Check installed version

apt-cache policy koji || rpm -q koji || koji --version

2. No fixed release: DOWNGRADE to a release before 1.13.0 (Debian / Ubuntu)

apt-cache madison koji sudo apt install koji=<VERSION_BEFORE_1.13.0> sudo apt-mark hold koji

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list koji sudo dnf downgrade koji-<VERSION_BEFORE_1.13.0> sudo dnf versionlock add koji

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-1002153?

koji: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-1002153 being exploited?

CVE-2017-1002153 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-1002153 affect?

CVE-2017-1002153 affects koji. Severity is high (CVSS 7.5). Koji 1.13.0 does not properly validate SCM paths, allowing an attacker to work around blacklisted paths for build submission.

How urgent is CVE-2017-1002153?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-17109 MEDIUM 6.5 UPGRADE Koji through 1.18.0 allows remote Directory Traversal, with resultant Privilege Escalation.
CVE-2019-10314 MEDIUM 5.9 UPGRADE Jenkins Koji Plugin disables SSL/TLS and hostname verification globally for the Jenkins master JVM.
CVE-2019-10298 HIGH 8.8 MITIGATE Jenkins Koji Plugin stores credentials unencrypted in its global configuration file on the Jenkins master wher
CVE-2018-1002150 CRITICAL 9.1 DOWNGRADE Koji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrar

References

← Back to latest CVEs