Pipeline\Application · Jenkins
CVE-2019-1003041
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 · uneditedA sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin 2.64 and earlier allows attackers to invoke arbitrary constructors in sandboxed scripts.
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 confidenceJenkins Pipeline: Groovy Plugin 2.64 and earlier contains a sandbox bypass vulnerability that allows attackers to invoke arbitrary constructors in sandboxed scripts. This enables circumvention of the Groovy sandbox security mechanism that normally restricts dangerous method calls 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
Pipeline\Application
<= 2.64
Openshift Container PlatformApplication
= 3.11CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Identify the Jenkins Pipeline: Groovy Plugin installationIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline: Groovy' or inspect the plugin files in $JENKINS_HOME/plugins/ directoryAffected if The plugin is present in the Jenkins installation
-
Determine the installed version of Pipeline: Groovy PluginIn the Jenkins plugin manager under the Installed tab, locate the Pipeline: Groovy plugin and note the version number displayedAffected if The installed version is 2.64 or earlier
-
Verify if Groovy sandbox execution is in useInspect Jenkins pipeline scripts (Jenkinsfile or inline scripts) for the directive 'groovy sandbox' or check if scripts run without explicitly disabling sandbox protectionAffected if Pipeline scripts are configured to use Groovy sandbox protection (the default behavior)
-
Confirm the OpenShift Container Platform version if applicableIf running Red Hat OpenShift Container Platform, check the OCP version via 'oc version' or the administrative consoleAffected if Running OpenShift Container Platform version 3.11 (which bundles the vulnerable plugin version)
You are affected if Pipeline: Groovy Plugin version 2.64 or earlier is installed and your pipeline scripts utilize Groovy sandbox protection (the default sandboxing mechanism).
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.
dbcve · scopedUpgrade Jenkins Pipeline: Groovy Plugin to version 2.65 or later to patch the sandbox bypass vulnerability.
Pipeline: Groovy Plugin version 2.65 or later (or latest available)
- Identify all Jenkins controllers running Pipeline: Groovy Plugin version 2.64 or earlier
- Schedule a maintenance window for the update
- Backup Jenkins configuration and job definitions
- Navigate to Manage Jenkins > Manage Plugins > Available tab
- Locate Pipeline: Groovy Plugin in the plugin list
- If update available, click 'Download now and install after restart'
- Alternatively, download the plugin .hpi from Jenkins repository and upload via 'Advanced' tab
- Restart Jenkins to complete the plugin update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003041 — 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-1003041 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