CVE-2022-43402 json
Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution
published 4y ago modified 4mo ago also GHSA-mqc2-w9r8-mmxm , EUVD-2022-7132
- cvss
- 9.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
A sandbox bypass vulnerability involving various casts performed implicitly by the Groovy language runtime in Jenkins Pipeline: Groovy Plugin 2802.v5ea_628154b_c2 and earlier allows attackers with permission 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.
Patch / fix
- maven org.jenkins-ci.plugins.workflow:workflow-cps 2803.v1a_f77ffcc773
- Jenkins project Jenkins Pipeline: Groovy Plugin 2746.2748.v365128b_c26d7, 2759.2761.vd6e8d2a_15980
- jenkins openshift 4.9 2.361.1.1675668150-1.el8
- jenkins-2-plugins openshift 4.9 4.9.1675668922-1.el8
- jenkins ocp tools 4.11 2.387.1.1683009763-3.el8
- jenkins-2-plugins ocp tools 4.11 4.11.1683009941-1.el8
- jenkins-2-plugins openshift 4.10 4.10.1675144701-1.el8
- jenkins-2-plugins ocp tools 4.12 4.12.1675702407-1.el8
red hat advisories RHSA-2023:0777RHSA-2023:3198RHSA-2023:0560RHSA-2023:1064
Is CVE-2022-43402 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-43402 updated cvss 9.9
jenkins-plugin/workflow-cps: Sandbox bypass vulnerabilities in Pipeline: Groovy Plugin
-
Red Hat OpenShift Container Platform 3.11 jenkins-2-pluginsaffected: no fix planned “Out of support scope”
-
Red Hat OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8 jenkins-2-plugins 4.11.1683009941-1.el8fixed: vendor fix RHSA-2023:3198
-
Red Hat OpenShift Developer Tools and Services for OCP 4.12 jenkins-2-plugins 4.12.1675702407-1.el8fixed: vendor fix RHSA-2023:1064
-
Red Hat OpenShift Container Platform 4.9 jenkins-2-plugins 4.9.1675668922-1.el8fixed: vendor fix RHSA-2023:0777
-
Red Hat OpenShift Container Platform 4.10 jenkins-2-plugins 4.10.1675144701-1.el8fixed: vendor fix RHSA-2023:0560
-
Red Hat OpenShift Developer Tools and Services for OCP 4.11 for RHEL 8 jenkins 2.387.1.1683009763-3.el8 Red Hat OpenShift Developer Tools and Services for OCP 4.12 jenkins 2.361.4.1675702346-3.el8 Red Hat OpenShift Container Platform 4.9 jenkins 2.361.1.1675668150-1.el8 Red Hat OpenShift Container Platform 4.10 cri-o 1.23.5-5.rhaos4.10.gitd9dec98.el7, cri-o 1.23.5-5.rhaos4.10.gitd9dec98.el8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins.workflow:workflow-cps | <2803.v1a_f77ffcc773 |
2803.v1a_f77ffcc773 |
Affected products
- Jenkins project Jenkins Pipeline: Groovy Plugin
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
jenkins.io
/security/advisory/2022-10-19/#SECURITY-2824%20%281%29
vendor-advisory
-
openwall.com
/lists/oss-security/2022/10/19/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-43402
advisory
-
jenkins.io
/security/advisory/2022-10-19/#SECURITY-2824%20(1)
web
Sources
- CVE List CVE-2022-43402
- GitHub Advisory GHSA-mqc2-w9r8-mmxm
- NVD CVE-2022-43402
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.