CVE-2022-25183: Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create cache director
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven) 561.va_ce0de3c2d69; jenkins (Red Hat:openshift:3.11::el7) 0:2.319.3.1650348949-1.el7; jenkins-2-plugins (Red Hat:openshift:3.11::el7) 0:3.11.1650371376-1.el7.
Low priority for now. Upgrade to org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven) 561.va_ce0de3c2d69; jenkins (Red Hat:openshift:3.11::el7) 0:2.319.3.1650348949-1.el7; jenkins-2-plugins (Red Hat:openshift:3.11::el7) 0:3.11.1650371376-1.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create cache directories without any sanitization, allowing attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM using specially crafted library names if a global Pipeline library configured to use caching already exists.
- Published
- Feb 15, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.5% · 75th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jenkins | pipeline\ | cpe:2.3:a:jenkins:pipeline\ |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jenkins pipeline:shared groovy librariesup to 552.vd9cc05b8a2e1 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (jenkins). Independent of NVD's CPE analysis and usually ahead of it.
Jenkins project Jenkins Pipeline: Shared Groovy Libraries Plugin
- 2.21.1not affected
- unspecified and later · up to and including 552.vd9cc05b8a2e1affected
- 2.21 and later · before unspecifiedaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.jenkins-ci.plugins.workflow:workflow-cps-global-lib | before 561.va_ce0de3c2d69 | 561.va_ce0de3c2d69 |
| Red Hat:openshift:3.11::el7 | jenkins | before 0:2.319.3.1650348949-1.el7 | 0:2.319.3.1650348949-1.el7 |
| Red Hat:openshift:3.11::el7 | jenkins-2-plugins | before 0:3.11.1650371376-1.el7 | 0:3.11.1650371376-1.el7 |
| Red Hat:openshift:4.10::el8 | jenkins-2-plugins | before 0:4.10.1647505461-1.el8 | 0:4.10.1647505461-1.el8 |
| Red Hat:openshift:4.6::el7 | haproxy | before 0:2.0.16-3.el7 | 0:2.0.16-3.el7 |
| Red Hat:openshift:4.6::el7 | haproxy-debuginfo | before 0:2.0.16-3.el7 | 0:2.0.16-3.el7 |
| Red Hat:openshift:4.6::el7 | haproxy20 | before 0:2.0.16-3.el7 | 0:2.0.16-3.el7 |
| Red Hat:openshift:4.6::el8 | haproxy | before 0:2.0.16-5.el8 | 0:2.0.16-5.el8 |
| Red Hat:openshift:4.6::el8 | haproxy-debugsource | before 0:2.0.16-5.el8 | 0:2.0.16-5.el8 |
| Red Hat:openshift:4.6::el8 | haproxy20 | before 0:2.0.16-5.el8 | 0:2.0.16-5.el8 |
| Red Hat:openshift:4.6::el8 | haproxy20-debuginfo | before 0:2.0.16-5.el8 | 0:2.0.16-5.el8 |
| Red Hat:openshift:4.6::el8 | jenkins-2-plugins | before 0:4.6.1650364520-1.el8 | 0:4.6.1650364520-1.el8 |
| Red Hat:openshift:4.7::el8 | jenkins-2-plugins | before 0:4.7.1648800585-1.el8 | 0:4.7.1648800585-1.el8 |
| Red Hat:openshift:4.8::el7 | cri-o | before 0:1.21.5-3.rhaos4.8.gitaf64931.el7 | 0:1.21.5-3.rhaos4.8.gitaf64931.el7 |
| Red Hat:openshift:4.8::el7 | cri-o-debuginfo | before 0:1.21.5-3.rhaos4.8.gitaf64931.el7 | 0:1.21.5-3.rhaos4.8.gitaf64931.el7 |
| Red Hat:openshift:4.8::el8 | cri-o | before 0:1.21.5-3.rhaos4.8.gitaf64931.el8 | 0:1.21.5-3.rhaos4.8.gitaf64931.el8 |
| Red Hat:openshift:4.8::el8 | cri-o-debuginfo | before 0:1.21.5-3.rhaos4.8.gitaf64931.el8 | 0:1.21.5-3.rhaos4.8.gitaf64931.el8 |
| Red Hat:openshift:4.8::el8 | cri-o-debugsource | before 0:1.21.5-3.rhaos4.8.gitaf64931.el8 | 0:1.21.5-3.rhaos4.8.gitaf64931.el8 |
| Red Hat:openshift:4.8::el8 | jenkins-2-plugins | before 0:4.8.1646993358-1.el8 | 0:4.8.1646993358-1.el8 |
| Red Hat:openshift:4.9::el8 | haproxy | before 0:2.2.15-4.el8 | 0:2.2.15-4.el8 |
| Red Hat:openshift:4.9::el8 | haproxy-debugsource | before 0:2.2.15-4.el8 | 0:2.2.15-4.el8 |
| Red Hat:openshift:4.9::el8 | haproxy22 | before 0:2.2.15-4.el8 | 0:2.2.15-4.el8 |
| Red Hat:openshift:4.9::el8 | haproxy22-debuginfo | before 0:2.2.15-4.el8 | 0:2.2.15-4.el8 |
| Red Hat:openshift:4.9::el8 | jenkins-2-plugins | before 0:4.9.1647580879-1.el8 | 0:4.9.1647580879-1.el8 |
Same product
jenkins: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-1003030A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/woKEV98Now
- CVE-2019-1003001A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlo61This week
- CVE-2019-1003002A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in pipeline-model-definition/src/main/groovy/org/jen59Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-25181Feb 15, 2022 · A sandbox bypass vulnerability in Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier allows attackers with Item/35Monitor
- ← EarlierCVE-2022-25182Feb 15, 2022 · A sandbox bypass vulnerability in Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier allows attackers with Item/35Monitor
- Later →CVE-2022-25184Feb 15, 2022 · Jenkins Pipeline: Build Step Plugin 2.15 and earlier reveals password parameter default values when generating a pipeline script using the P26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.jenkins-ci.plugins.workflow:workflow-cps-global-lib | 561.va_ce0de3c2d69 | Package registry (OSV) |
| red hat:cri-o | 0:1.21.5-3.rhaos4.8.gitaf64931.el7 · Red Hat:openshift:4.8::el7 | Package registry (OSV) |
| red hat:cri-o-debuginfo | 0:1.21.5-3.rhaos4.8.gitaf64931.el7 · Red Hat:openshift:4.8::el7 | Package registry (OSV) |
| red hat:cri-o-debugsource | 0:1.21.5-3.rhaos4.8.gitaf64931.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:haproxy | 0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8 | Package registry (OSV) |
| red hat:haproxy-debuginfo | 0:2.0.16-3.el7 · Red Hat:openshift:4.6::el7 | Package registry (OSV) |
| red hat:haproxy-debugsource | 0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8 | Package registry (OSV) |
| red hat:haproxy20 | 0:2.0.16-3.el7 · Red Hat:openshift:4.6::el7 | Package registry (OSV) |
| red hat:haproxy20-debuginfo | 0:2.0.16-5.el8 · Red Hat:openshift:4.6::el8 | Package registry (OSV) |
| red hat:haproxy22 | 0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8 | Package registry (OSV) |
| red hat:haproxy22-debuginfo | 0:2.2.15-4.el8 · Red Hat:openshift:4.9::el8 | Package registry (OSV) |
| red hat:jenkins | 0:2.319.3.1650348949-1.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.8.1646993358-1.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.