KojiApplication · Jenkins
CVE-2019-10314
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 · uneditedJenkins Koji Plugin disables SSL/TLS and hostname verification globally for the Jenkins master JVM.
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 confidenceThe Jenkins Koji Plugin disables SSL/TLS certificate and hostname verification globally for the entire Jenkins master JVM, not just for its own connections. This affects all outbound HTTPS communications from Jenkins, creating a widespread man-in-the-middle vulnerability across the entire Jenkins instance.
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
<= 0.3CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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.
-
Check if Koji plugin is installedList installed plugins via Jenkins CLI: 'jenkins-cli.jar -s http://[jenkins-url] list-plugins' or inspect the JENKINS_HOME/plugins directory for a directory or .jpi file named 'koji'Affected if Koji plugin is not found in the installed plugins list
-
Determine Koji plugin versionRun 'jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep -i koji' or read the plugin's manifest file (META-INF/MANIFEST.MF) inside the JENKINS_HOME/plugins/koji.jpi fileAffected if Installed version is 0.3 or lower, or version cannot be determined (indicating an old unversioned release)
-
Inspect plugin for SSL verification disablement codeExtract the koji.hpi/.jpi file and search source code for 'DisabledSSLVerification' or 'trustManager' or 'HostnameVerifier' configuration that applies to the entire JVM (not just plugin-specific connections)Affected if Code that disables SSL certificate or hostname verification is present in the plugin's configuration or initialization routines
A user is affected if they have the Koji plugin installed at version 0.3 or lower, and the plugin contains code that globally disables SSL/TLS verification for all Jenkins outbound HTTPS connections.
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 dataEither update to a patched version of the Koji Plugin that removes the global verification disablement, or implement compensating network-level controls (such as trusted internal PKI) to protect other Jenkins outbound HTTPS connections from MITM attacks.
Fix this in Koji
Scoped from the published advisory
- 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-10314 — 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-10314 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