CVE-2019-17109
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 · uneditedKoji through 1.18.0 allows remote Directory Traversal, with resultant Privilege Escalation.
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 · moderate confidenceKoji through version 1.18.0 contains a remote directory traversal vulnerability that allows authenticated remote attackers to access files and directories outside the intended web root, leading to privilege escalation through unauthorized access to sensitive system files or elevated functionality.
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<= 1.18.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Koji versionRun 'koji --version' or check the installed package version via your system's package manager (e.g., 'rpm -q koji' or 'pip show koji'). Compare the version number to the affected range (1.18.0 or earlier).Affected if The installed version is 1.18.0 or any earlier version.
-
Verify Koji web interface is exposedConfirm that Koji Hub (the web component) is running and accessible on your network. Check your web server configuration for koji-web/koji-hub virtual hosts or proxied endpoints.Affected if The Koji web interface is externally accessible or accessible to authenticated users.
-
Check for authentication mechanismReview your Koji configuration to determine if user authentication (Kerberos, SSL certificates, or password-based) is enabled for the web interface.Affected if Users can authenticate to the Koji web interface, as the vulnerability requires authenticated access.
-
Inspect file path handling in web requestsExamine the Koji Hub code or HTTP access logs for any file download or path-related requests that accept user-supplied path parameters. Look for patterns like 'path=', 'file=', or similar parameters.Affected if The web interface accepts and processes file path parameters without proper validation.
Your environment is affected if Koji version 1.18.0 or earlier is installed, the web interface is accessible, and users can authenticate to trigger directory traversal via path parameters.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a patched version beyond 1.18.0. Implement strict input validation on file path parameters and enforce proper access controls on filesystem operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17109 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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