CVE-2022-43405

Pipeline: Groovy Libraries Plugin and older releases of the Pipeline: Deprecated Groovy Libraries Plugin (formerly Pipeline: Shared Groovy Libraries Plugin) define the library Pipeline step, which allows Pipeline authors to dynamically load Pipeline libraries. The return value of this step can be used to instantiate classes defined in the loaded library.

In Pipeline: Groovy Libraries Plugin 612.v84da_9c54906d and earlier and in Pipeline: Deprecated Groovy Libraries Plugin 583.vf3b_454e43966 and earlier, the library step can be used to invoke sandbox-generated synthetic constructors in crafted untrusted libraries and construct any subclassable type. This is similar to SECURITY-582 in the 2017-08-07 security advisory, but in a different plugin.

This vulnerability allows attackers with permission to define untrusted Pipeline libraries and to define and run sandboxed Pipelines, to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.

Pipeline: Groovy Libraries Plugin 613.v9c41a_160233f rejects improper calls to sandbox-generated synthetic constructors when using the library step.

Pipeline: Deprecated Groovy Libraries Plugin 588.v576c103a_ff86 no longer contains the library step. It has been moved into the Pipeline: Groovy Libraries Plugin.

CVE-2022-43405 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (613.v9c41a_160233f, 588.v576c103a_ff86); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2022-43405? CVE-2022-43405 is a high-severity security vulnerability in io.jenkins.plugins:pipeline-groovy-lib (maven), affecting versions < 613.v9c41a. It is fixed in 613.v9c41a_160233f, 588.v576c103a_ff86.
2. How severe is CVE-2022-43405? CVE-2022-43405 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-43405?
   • io.jenkins.plugins:pipeline-groovy-lib (maven) (versions < 613.v9c41a)
   • org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (maven) (versions <= 583.vf3b)
4. Is there a fix for CVE-2022-43405? Yes. CVE-2022-43405 is fixed in 613.v9c41a_160233f, 588.v576c103a_ff86. Upgrade to this version or later.
5. Is CVE-2022-43405 exploitable, and should I be worried? Whether CVE-2022-43405 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-43405 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-43405?
   • Upgrade io.jenkins.plugins:pipeline-groovy-lib to 613.v9c41a_160233f or later
   • Upgrade org.jenkins-ci.plugins.workflow:workflow-cps-global-lib to 588.v576c103a_ff86 or later