dbcve.org
Kubernetes PipelineApplication · Jenkins

CVE-2019-10417

CRITICAL · 9.9 CVSS v3.1 Published 2019-09-25
Fix available
A fix is available. Upgrade to after 1.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Jenkins Kubernetes :: Pipeline :: Kubernetes Steps Plugin provides a custom whitelist for script security that allowed attackers to invoke arbitrary methods, bypassing typical sandbox protection.

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

The Jenkins Kubernetes Pipeline Steps Plugin contained a flawed custom whitelist for script security that allowed attackers to invoke arbitrary methods on objects, effectively bypassing Jenkins' typical sandbox protection and enabling remote code execution.

MitigationUpdate the Kubernetes Steps Plugin to the patched version immediately. Review and restrict pipeline script permissions until the update is applied.

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
Kubernetes PipelineApplication
Affected:<= 1.6

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify if Kubernetes Pipeline Steps Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed and look for 'Kubernetes Pipeline Steps' or 'kubernetes-steps' plugin
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version of the Kubernetes Pipeline Steps Plugin
    In the Installed plugins list, note the version number shown for the Kubernetes Pipeline Steps plugin
    Affected if The version is 1.6 or lower
  3. Verify if script security sandbox is in use for pipeline scripts
    Review Jenkins pipeline configurations for 'script security' or 'sandbox' settings, or check if pipelines use @Library or untrusted scripted steps
    Affected if Pipelines run with script security/sandbox enabled, since the vulnerability bypasses this protection
  4. Confirm pipeline execution permissions exist for untrusted users
    Check if any users or groups have permission to create or run Jenkins pipelines who are not fully trusted administrators
    Affected if Non-admin users or external contributors can run pipeline scripts
  5. Inspect for use of Kubernetes-related steps in pipelines
    Review existing Jenkinsfile or pipeline definitions for use of kubernetes-specific steps like 'kubectl', 'container', or kubernetes deployment commands
    Affected if Pipelines use kubernetes steps from the affected plugin

You are affected if the Kubernetes Pipeline Steps Plugin version 1.6 or lower is installed AND pipelines with script security sandbox can be executed by users who are not fully trusted administrators.

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
Upgrade available Upgrade to a release after 1.6
Interim mitigation

Update the Kubernetes Steps Plugin to the patched version immediately. Review and restrict pipeline script permissions until the update is applied.

Recommended fix Moderate confidence

Kubernetes Pipeline plugin version 1.7 or later

  1. 1. Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Locate 'Kubernetes Pipeline' (or 'Kubernetes :: Pipeline :: Kubernetes Steps') plugin
  4. 4. If update available, click 'Update' to upgrade to version 1.7 or later
  5. 5. Restart Jenkins to complete the installation
  6. 6. Alternatively, download the fixed plugin from the Jenkins Update Center and manually install via 'Advanced' > 'Upload Plugin'

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

Fix this in Kubernetes Pipeline Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10417 — 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-2019-10417 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