# CVE-2022-25173: Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin > Attackers with Item/Configure permission can execute arbitrary OS commands on the Jenkins controller via crafted SCM contents due to shared checkout directories. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Feb 2022 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-4m7p-55jm-3vwv ## What is CVE-2022-25173? CVE-2022-25173 is a high-severity command injection vulnerability in Jenkins Pipeline: Groovy Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier 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. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2022-25173? 6 open source packages ship an affected version, including org.jenkins-ci.plugins.workflow:workflow-cps. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | All versions | 2.92.1 | | `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | All versions | 2.92.1 | | `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | From 2.93 | 2.94.1 | | `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | From 2.93 | 2.94.1 | | `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | From 2646.v6ed3b5b01ff1 | 2656.vf7a | | `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | From 2646.v6ed3b5b01ff1 | 2656.vf7a | Products: Jenkins Pipeline\. ## How do I fix CVE-2022-25173? Upgrade org.jenkins-ci.plugins.workflow:workflow-cps to a fixed version for your release line: 2.92.1, 2.94.1 or 2656.vf7a. ## Is CVE-2022-25173 being exploited? There is no known exploitation of CVE-2022-25173 in the wild and no public exploit code. Public exploit code: - https://github.com/shoucheng3/jenkinsci__workflow-cps-plugin_CVE-2022-25173_2646-v6ed3b5b01ff1 (github_poc): https://github.com/shoucheng3/jenkinsci__workflow-cps-plugin_CVE-2022-25173_2646-v6ed3b5b01ff1 ## Other vulnerabilities in Jenkins Pipeline: Groovy Plugin - [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild) - [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9) - [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8) - [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8) - [CVE-2022-25174](https://insights.sbomify.com/CVE-2022-25174/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Shared Groovy Libraries Plugin (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-25173 and fix it if it is affected. What it is: CVE-2022-25173 is a high-severity command injection vulnerability in Jenkins Pipeline: Groovy Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-25173 in the wild and no public exploit code. Affected packages and fixed versions: - org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected all versions; fixed in 2.92.1 - org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected all versions; fixed in 2.92.1 - org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected from 2.93; fixed in 2.94.1 - org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected from 2.93; fixed in 2.94.1 - org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected from 2646.v6ed3b5b01ff1; fixed in 2656.vf7a - org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected from 2646.v6ed3b5b01ff1; fixed in 2656.vf7a Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-25173/ (Markdown: https://insights.sbomify.com/CVE-2022-25173/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25173 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25173 - OSV: https://osv.dev/vulnerability/CVE-2022-25173 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-25173/ Summaries are generated and may contain mistakes; the official description above is the record.