CVE-2022-30945: Jenkins Pipeline: Groovy Plugin 2689.v434009a_31b_f1 and earlier allows loading any Groovy source files on the classpath of Jenkins and Jenk
Noroxi assessment
Priority: Monitor (action score 34/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.4% (FIRST EPSS); higher than 72.6% 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. Special conditions such as timing or configuration are required.
- Fixed version: org.jenkins-ci.plugins.workflow:workflow-cps (Maven) 2692.v76b; jenkins (Red Hat:openshift:4.8::el8) 0:2.361.1.1672840472-1.el8; jenkins-2-plugins (Red Hat:openshift:4.8::el8) 0:4.8.1672842762-1.el8.
Low priority for now. Upgrade to org.jenkins-ci.plugins.workflow:workflow-cps (Maven) 2692.v76b; jenkins (Red Hat:openshift:4.8::el8) 0:2.361.1.1672840472-1.el8; jenkins-2-plugins (Red Hat:openshift:4.8::el8) 0:4.8.1672842762-1.el8 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: Groovy Plugin 2689.v434009a_31b_f1 and earlier allows loading any Groovy source files on the classpath of Jenkins and Jenkins plugins in sandboxed pipelines.
- Published
- May 17, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.4% · 72th percentile
- CWE
- —
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
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: groovybefore 2689.v434009a_31b_f1
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: Groovy Plugin
- 2683.2687.vb_0cc3f973f06, 2.94.4not affected
- unspecified and later · up to and including 2689.v434009a_31b_f1affected
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 | before 2692.v76b | 2692.v76b |
| Red Hat:openshift:4.8::el8 | jenkins | before 0:2.361.1.1672840472-1.el8 | 0:2.361.1.1672840472-1.el8 |
| Red Hat:openshift:4.8::el8 | jenkins-2-plugins | before 0:4.8.1672842762-1.el8 | 0:4.8.1672842762-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-28158Mar 29, 2022 · A missing permission check in Jenkins Pipeline: Phoenix AutoTest Plugin 1.3 and earlier allows attackers with Overall/Read permission to enu26Monitor
- ← EarlierCVE-2022-29047Apr 12, 2022 · Jenkins Pipeline: Shared Groovy Libraries Plugin 564.ve62a_4eb_b_e039 and earlier, except 2.21.3, allows attackers able to submit pull reque21Monitor
- Later →CVE-2022-34177Jun 23, 2022 · Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` step31Monitor
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 | 2692.v76b | Package registry (OSV) |
| red hat:jenkins | 0:2.361.1.1672840472-1.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.8.1672842762-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.