CVE-2022-25173

Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin

Jenkins Pipeline: Groovy Plugin prior to 2656.vf7a_e7b_75a_457, 2.94.1, and 2.92.1 uses the same checkout directories for distinct SCMs when reading the script file (typically Jenkinsfile) for Pipelines, allowing attackers with Item/Configure permission to invoke arbitrary OS commands on the controller through crafted SCM contents.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2022-25173 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 (2656.vf7a, 2.94.1, 2.92.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2022-25173? CVE-2022-25173 is a high-severity OS command injection vulnerability in org.jenkins-ci.plugins.workflow:workflow-cps (maven), affecting versions >= 2646.v6ed3b5b01ff1, < 2656.vf7a. It is fixed in 2656.vf7a, 2.94.1, 2.92.1. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2022-25173? CVE-2022-25173 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 versions of org.jenkins-ci.plugins.workflow:workflow-cps are affected by CVE-2022-25173? org.jenkins-ci.plugins.workflow:workflow-cps (maven) versions >= 2646.v6ed3b5b01ff1, < 2656.vf7a is affected.
4. Is there a fix for CVE-2022-25173? Yes. CVE-2022-25173 is fixed in 2656.vf7a, 2.94.1, 2.92.1. Upgrade to this version or later.
5. Is CVE-2022-25173 exploitable, and should I be worried? Whether CVE-2022-25173 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-25173 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-25173?
   • Upgrade org.jenkins-ci.plugins.workflow:workflow-cps to 2656.vf7a or later
   • Upgrade org.jenkins-ci.plugins.workflow:workflow-cps to 2.94.1 or later
   • Upgrade org.jenkins-ci.plugins.workflow:workflow-cps to 2.92.1 or later

Other vulnerabilities in org.jenkins-ci.plugins.workflow:workflow-cps