dbcve.org
KojiApplication · Koji Project

CVE-2018-1002150

CRITICAL · 9.1 CVSS v3.0 Published 2018-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Koji build system versions 1.12-1.15 contain an incorrect access control vulnerability allowing authenticated users to perform arbitrary filesystem read/write operations due to improper permission validation in the filesystem handling code.

MitigationImmediately upgrade Koji to versions 1.12.1, 1.13.1, 1.14.1, or 1.15.1 or later to patch the access control flaw. Review user access permissions and audit system logs for signs of exploitation given the critical CVSS score.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KojiApplication
Affected:= 1.12.0= 1.13.0= 1.14.0= 1.15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Koji installation
    Check if the Koji build system is installed by looking for the 'koji' command or checking for the presence of /etc/koji.conf or /etc/koji-hub.conf configuration files. On RPM-based systems, run: rpm -qa | grep -i koji
    Affected if Koji is not installed or the commands/config files are not found, then this CVE does not apply to your environment.
  2. Determine Koji version
    Run 'koji --version' or check the RPM package version with 'rpm -qa | grep -i koji' to identify the exact installed version
    Affected if The installed version is exactly 1.12.0, 1.13.0, 1.14.0, or 1.15.0, indicating vulnerability to this CVE.
  3. Confirm filesystem handling is enabled
    Check if the filesystem handling module is enabled by reviewing /etc/koji-hub.conf or /etc/koji.conf for 'fsAlias' or 'filesystem' related configurations. Also check if the 'koji-hub' service is running with filesystem-related tasks enabled.
    Affected if The filesystem handling feature is configured and active in the Koji environment, which is required for the vulnerability to be exploitable.
  4. Check authentication configuration
    Review /etc/koji-hub.conf to determine how user authentication is configured. Verify if the system allows authenticated user access. Look for EnableSSLAuth, MaxSessionAge, or similar authentication settings.
    Affected if The system allows authenticated user sessions (not fully restricted to admin-only), which is a precondition for authenticated users to exploit the access control flaw.

You are affected if Koji is installed with version 1.12.0, 1.13.0, 1.14.0, or 1.15.0 and the filesystem handling feature is enabled for authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade Koji to versions 1.12.1, 1.13.1, 1.14.1, or 1.15.1 or later to patch the access control flaw. Review user access permissions and audit system logs for signs of exploitation given the critical CVSS score.

Recommended fix High confidence

Upgrade to Koji version 1.15.1 (or the corresponding 1.12.1, 1.13.1, or 1.14.1 for your respective base version)

  1. 1. Identify the currently installed Koji version using: rpm -q koji or pip show koji
  2. 2. Backup the current Koji installation and database
  3. 3. Upgrade Koji to the fixed version using the appropriate package manager command: yum update koji (for RHEL/CentOS) or pip install --upgrade koji
  4. 4. Verify the new version is installed: rpm -q koji or pip show koji
  5. 5. Restart the Koji hub and related services: systemctl restart httpd (or your web server) and any koji-* services
  6. 6. Test that the Koji instance is functioning correctly and that the arbitrary filesystem read/write vulnerability is no longer present
Caveat Minor version upgrade with bug and security fixes; standard upgrade precautions (backup, testing in non-production first) recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Koji Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1002150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1002150 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data