Pipeline\Application · Jenkins
CVE-2022-43402
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 involving various casts performed implicitly by the Groovy language runtime in Jenkins Pipeline: Groovy Plugin 2802.v5ea_628154b_c2 and earlier allows attackers with permission to define and run sandboxed scripts, including Pipelines, to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller 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 · high confidenceThe Jenkins Pipeline: Groovy Plugin contains a sandbox bypass vulnerability where implicit type casts performed by the Groovy runtime can be exploited to circumvent sandbox restrictions. Attackers with permission to define and run sandboxed scripts (including Pipelines) can bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.
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
<= 2802.v5ea_628154b_c2CVSS 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.
-
Identify if Pipeline: Groovy Plugin is installedLog into Jenkins and navigate to Manage Jenkins > Manage Plugins > Installed, then search for 'Pipeline: Groovy' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn the same Installed Plugins view, locate the 'Pipeline: Groovy' entry and note the Version column value displayedAffected if The version listed is 2802.v5ea_628154b_c2 or any version number that is lexicographically lower (e.g., 2801.x, 2700.x, etc.)
-
Verify plugin is enabled and activeConfirm the plugin Status shows 'Enabled' and there are no pending restarts that would disable it. Alternatively, check $JENKINS_HOME/plugins/pipeline-groovy*/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if The plugin is enabled and active with a vulnerable version
-
Confirm script execution permissions existReview users or jobs that have permission to create or run Pipeline scripts or sandboxed scripts (Jobs > Configure > Pipeline Script or 'Groovy Sandbox' checkbox enabled)Affected if Any user or automated process has permission to define and execute sandboxed Pipeline scripts
You are affected if the Pipeline: Groovy plugin is installed with version 2802.v5ea_628154b_c2 or lower and any user or job has permission to execute sandboxed scripts.
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 Jenkins Pipeline: Groovy Plugin to version 2802.v5ea_628154b_c2 or later to remediate the vulnerability.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43402 — 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-2022-43402 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