dbcve.org
Groovy LibrariesApplication · Jenkins

CVE-2022-43405

CRITICAL · 9.9 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 612.v84da_9c54906d 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
A sandbox bypass vulnerability in Jenkins Pipeline: Groovy Libraries Plugin 612.v84da_9c54906d and earlier allows attackers with permission to define untrusted Pipeline libraries and 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 confidence

A sandbox bypass vulnerability in Jenkins Pipeline: Groovy Libraries Plugin allows attackers with specific permissions to define untrusted Pipeline libraries and run sandboxed scripts to bypass sandbox protections and execute arbitrary code on the Jenkins controller JVM.

MitigationUpdate Jenkins Pipeline: Groovy Libraries Plugin to version 613.vd_3fa_64d8c0b_92 or later, and review user permissions for Pipeline library definitions and sandboxed script execution.

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
Groovy LibrariesApplication
Affected:<= 612.v84da_9c54906d

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. Verify Pipeline: Groovy Libraries Plugin version
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, locate 'Pipeline: Groovy Libraries' (or Groovy Libraries Plugin), and note the version. Alternatively, run this in the Script Console: Jenkins.instance.pluginManager.plugins.find{it.shortName=='pipeline-groovy-libs'?.version
    Affected if The installed version is 612.v84da_9c54906d or lower (versions through 612.v84da_9c54906d are vulnerable)
  2. Confirm shared libraries are configured
    Go to Manage Jenkins > System > Global Pipeline Libraries, or check Jenkinsfile for @Library annotations. Alternatively, query via API: GET /jenkins/loadedGroovyLibs/ or review /var/jenkins_home/libraries if using filesystem-based libraries.
    Affected if Any Pipeline shared libraries are defined (trusted or untrusted), as the vulnerability allows bypassing sandbox protections when library methods are called from sandboxed scripts
  3. Review user permissions for library definition
    Go to Manage Jenkins > Manage Users and Manage Jenkins > Configure Global Security. Check if any users or groups have the 'Libraries' permission (libraryDefinition permission) or are able to create/modify Pipeline libraries. In script console: Jenkins.instance.authorizationStrategy.permissions.each { if (it.name.contains('LIBRARY')) println it }
    Affected if Non-admin users or service accounts have permissions to define or modify Pipeline libraries
  4. Check for sandboxed Pipeline script execution
    Review job configurations for Pipelines using 'Pipeline script' (not 'Pipeline script from SCM'). Check if Groovy sandbox is enabled in job settings. Run in Script Console: Jenkins.instance.items.findAll { it instanceof org.jenkinsci.plugins.workflow.flow.FlowExecutionOwner }.each { println it.job.name }
    Affected if Any Pipeline jobs use sandboxed scripts that can call into shared library methods
  5. Identify untrusted library usage in sandboxed pipelines
    Review Pipeline jobs that use @Library('libraryName') syntax and have groovy sandbox enabled. Check job configurations for 'Use Groovy Sandbox' checkbox under Pipeline script settings. Query via API or review job config XML files in $JENKINS_HOME/jobs/
    Affected if Sandboxed Pipeline scripts reference shared library methods from untrusted or externally-defined libraries

You are affected if the Pipeline: Groovy Libraries Plugin version is 612.v84da_9c54906d or lower AND untrusted users have library definition permissions OR sandboxed Pipeline scripts can invoke shared library methods.

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 612.v84da_9c54906d
Interim mitigation

Update Jenkins Pipeline: Groovy Libraries Plugin to version 613.vd_3fa_64d8c0b_92 or later, and review user permissions for Pipeline library definitions and sandboxed script execution.

Recommended fix High confidence

Pipeline: Groovy Libraries plugin 615.v3b_1a_4d0c0f6 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Locate 'Pipeline: Groovy Libraries' plugin
  4. 4. If updates are available, click 'Update' to install the latest version
  5. 5. Restart Jenkins controller after the update completes
  6. 6. Verify the plugin version is newer than 612.v84da_9c54906d under Manage Jenkins > Manage Plugins > Installed

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

Fix this in Groovy Libraries Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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