Pipeline\Application · Jenkins

CVE-2022-29047

MEDIUM · 5.3 CVSS v3.1 Published 2022-04-12

Fix available

A fix is available. Upgrade to 2.21.3 / 566.vd0a_a_3334a_555 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Jenkins Pipeline: Shared Groovy Libraries Plugin 564.ve62a_4eb_b_e039 and earlier, except 2.21.3, allows attackers able to submit pull requests (or equivalent), but not able to commit directly to the configured SCM, to effectively change the Pipeline behavior by changing the definition of a dynamically retrieved library in their pull request, even if the Pipeline is configured to not trust them.

Technical summary

dbcve analysis · high confidence

The Jenkins Pipeline: Shared Groovy Libraries Plugin fails to properly isolate library code loaded from pull requests. Attackers with pull request access (but not direct SCM commit rights) can modify library definitions in their pull request to alter pipeline behavior, even when the pipeline is configured to not trust them. This allows code injection into trusted pipeline executions.

MitigationUpdate the Shared Groovy Libraries plugin to version 2.21.3 or later. Review all pipelines that use dynamically retrieved shared libraries and audit recent pull requests for suspicious changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Pipeline\Application

Affected:< 2.21.3>= 544.vff04fa68714d, < 566.vd0a_a_3334a_555

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check if Pipeline: Shared Groovy Libraries plugin is installed

Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins script console: Jenkins.instance.pluginManager.getPlugin('workflow-cps-global-lib').getVersion()

Affected if The plugin is not installed or the command returns null
Identify the installed plugin version

In Manage Jenkins > Manage Plugins > Installed, find 'Pipeline: Shared Groovy Libraries' and note the version column. Alternatively, run: Jenkins.instance.pluginManager.getPlugin('workflow-cps-global-lib').manifest.getAttribute('Implementation-Version')

Affected if Version is less than 2.21.3, or falls in range 544.vff04fa68714d to 566.vd0a_a_3334a_555
Identify pipelines using shared libraries with pull request retrieval

Search pipeline configurations (Jenkinsfile or pipeline job settings) for 'library' steps that specify 'retriever: trustedpullrequest()' or similar pull request retrieval modes. Check shared library global configurations under Manage Jenkins > Configure System > Global Pipeline Libraries for PR-enabled retrieval

Affected if Any shared library is configured to load from pull requests
Check trust configuration for shared library retrieval

Inspect the library definition in Jenkinsfiles or global library configuration. Look for parameters like 'trust' set to 'default', 'new', or unspecified, which may indicate untrusted PR code could execute

Affected if Libraries are configured to load from pull requests without explicit trust restrictions, or trust is set to 'default'
Review recent pipeline executions from pull request sources

Check build history for runs triggered by pull request events. Inspect console output and any shared library code that was loaded. Look for unexpected behavior or unauthorized code execution

Affected if Pipelines have recently run using libraries from pull requests, especially if the library version changed during the PR

A user is affected if the Pipeline: Shared Groovy Libraries plugin version is below 2.21.3 (or in the range 544.vff04fa68714d to 566.vd0a_a_3334a_555) AND any pipeline or shared library configuration enables loading code from pull requests.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2.21.3 / 566.vd0a_a_3334a_555 or later

Fixed in 2.21.3566.vd0a_a_3334a_555

Interim mitigation

Update the Shared Groovy Libraries plugin to version 2.21.3 or later. Review all pipelines that use dynamically retrieved shared libraries and audit recent pull requests for suspicious changes.

Recommended fix High confidence

1. Identify the current version of the Pipeline: Shared Groovy Libraries plugin in Jenkins: Go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Pipeline: Shared Groovy Libraries'
2. If running version 564.ve62a_4eb_b_e039 or earlier (except 2.21.3), or version 544.vff04fa68714d through 565.x, an upgrade is required
3. In Jenkins, go to Manage Jenkins > Manage Plugins > Available tab
4. Locate 'Pipeline: Shared Groovy Libraries' in the plugin list
5. Select the checkbox next to the plugin and click 'Download now and install after restart'
6. Wait for the download to complete, then restart Jenkins (or wait for the scheduled restart if configured)
7. After restart, verify the new version is installed: Go to Manage Jenkins > Manage Plugins > Installed and confirm the version shows 566.vd0a_a_3334a_555 or 2.21.3 or later

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
Testing4.0 h
Review / QA1.0 h

8.0 hours of engineering $1,360

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,176.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.jenkins.ioVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29047 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-29047?

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.

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

At a glance

A fix existsUpgrade to 2.21.3 / 566.vd0a_a_3334a_555 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 1.1%

Affects: Pipeline\

Remediation

Need this fixed?

Fix this in Pipeline\ 8 hrs · Low

Typical engagement from $1,360

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-29047 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References