Kubernetes PipelineApplication · Jenkins
CVE-2019-10418
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 Kubernetes :: Pipeline :: Arquillian 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 confidenceThe Jenkins Kubernetes :: Pipeline :: Arquillian Steps Plugin contained a custom script security whitelist that was overly permissive, allowing attackers to invoke arbitrary methods and bypass the standard Jenkins sandbox protection designed to restrict dangerous operations in pipeline scripts.
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
<= 1.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Kubernetes Pipeline plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i kubernetesAffected if The Kubernetes Pipeline plugin appears in the installed plugins list
-
Verify plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed, find 'Kubernetes :: Pipeline :: Arquillian Steps' and note the version number shownAffected if The installed version is 1.6 or lower
-
Confirm plugin is activeCheck Jenkins > Manage Plugins > Installed: the plugin status should show 'Enabled' or 'Active'Affected if The plugin is enabled and loaded by Jenkins
-
Review script execution logs for suspicious activityCheck Jenkins audit logs (if enabled) in $JENKINS_HOME/logs/ or via Manage Jenkins > System Log for executions of pipeline scripts using Kubernetes-related steps during the vulnerable periodAffected if Unexpected or unauthorized pipeline script executions are found that invoke methods beyond normal Kubernetes operations
The environment is affected if the Kubernetes :: Pipeline :: Arquillian Steps plugin is installed, enabled, and running at version 1.6 or lower, as this version contains an overly permissive script security whitelist that can be exploited to bypass Jenkins sandbox protection.
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 the plugin to the latest version which fixes the unsafe whitelist, or remove the plugin if not required. Review Jenkins audit logs for any suspicious script executions during the vulnerable period.
Fix this in Kubernetes Pipeline
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10418 — 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-10418 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