dbcve.org
Groovy LibrariesApplication · Jenkins

CVE-2022-43406

CRITICAL · 9.9 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 583.vf3b_454e43966 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: Deprecated Groovy Libraries Plugin 583.vf3b_454e43966 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: Deprecated Groovy Libraries Plugin versions 583.vf3b_454e43966 and earlier allows attackers with specific permissions (to define untrusted Pipeline libraries and to define/run sandboxed scripts) to bypass Jenkins sandbox protection and execute arbitrary code directly in the Jenkins controller JVM, granting full control over the controller.

MitigationUpgrade Jenkins Pipeline: Deprecated Groovy Libraries Plugin to version 583.vf3b_454e43966 or later. Additionally, restrict permissions for defining untrusted Pipeline libraries and sandboxed scripts to minimize the attack surface.

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:<= 583.vf3b_454e43966

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: Deprecated Groovy Libraries Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or list installed plugins via Jenkins CLI: jenkins-cli.jar or REST API /pluginManager/plugins/json
    Affected if The plugin appears in the installed plugins list
  2. Check plugin version
    In the Installed plugins tab, find 'Pipeline: Deprecated Groovy Libraries' and note the Version column. Alternatively, inspect the plugin file: $JENKINS_HOME/plugins/deprecated-groovy-libs.jpi (or .hpi) and read the MANIFEST.MF for the Implementation-Version
    Affected if Version is 583.vf3b_454e43966 or earlier, or the version cannot be determined (plugin likely older)
  3. Identify users with Pipeline library permissions
    Navigate to Manage Jenkins > Manage Users, or check the authorization matrix at Manage Jenkins > Configure Global Security. Look for permissions related to 'Library' or 'Script' such as 'Overall/RunScripts' or 'Pipeline: Extend Groovy Classpath' in the role-based or matrix-based security configuration
    Affected if More than one user or group has permissions to define untrusted Pipeline libraries in addition to running sandboxed scripts
  4. Confirm permission combination exists
    Review the user/group permissions to determine if a single attacker could have BOTH the ability to define untrusted Pipeline libraries AND the ability to define or run sandboxed Pipeline scripts
    Affected if The same user or group (or any user within the same permission set) has both capabilities enabled simultaneously

You are affected if the Pipeline: Deprecated Groovy Libraries Plugin version is 583.vf3b_454e43966 or earlier AND any user has both permissions to define untrusted Pipeline libraries and to run sandboxed scripts.

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.

From vendor data
Upgrade available Upgrade to a release after 583.vf3b_454e43966
Interim mitigation

Upgrade Jenkins Pipeline: Deprecated Groovy Libraries Plugin to version 583.vf3b_454e43966 or later. Additionally, restrict permissions for defining untrusted Pipeline libraries and sandboxed scripts to minimize the attack surface.

Fix this in Groovy Libraries Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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