dbcve.org
Pipeline\Application · Jenkins

CVE-2022-25181

HIGH · 8.8 CVSS v3.1 Published 2022-02-15
Fix available
A fix is available. Upgrade to after 552.vd9cc05b8a2e1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM through crafted SCM contents, if a global Pipeline library already exists.

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

A detailed technical summary for this CVE is being prepared.

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
Affected:<= 552.vd9cc05b8a2e1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 552.vd9cc05b8a2e1
Vendor patch www.jenkins.io →
Recommended fix High confidence

Pipeline: Shared Groovy Libraries plugin version 553.vd9cc05b8a2e1 or later

  1. 1. Back up your Jenkins instance and configuration before making any changes.
  2. 2. Navigate to Manage Jenkins > Manage Plugins.
  3. 3. Go to the 'Available' tab and search for 'Pipeline: Shared Groovy Libraries' plugin.
  4. 4. If the update is available, select the plugin and click 'Download now and install after restart' or 'Update'.
  5. 5. Alternatively, download the fixed plugin version (553.vd9cc05b8a2e1 or later) from the Jenkins plugin repository and manually upload it via 'Advanced' > 'Upload Plugin'.
  6. 6. Restart Jenkins to apply the update.
  7. 7. Verify the plugin version shows 553.vd9cc05b8a2e1 or later in 'Manage Plugins' > 'Installed' tab.
Caveat Review any shared library configurations after upgrade, as with any security fix that restricts previously allowed behavior

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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