CVE-2022-25174
HIGHCVE-2022-25174 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in org.jenkins-ci.plugins.workflow:workflow-cps-global-lib. O3 Security confirms whether CVE-2022-25174 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Shared Groovy Libraries Plugin
Real-World Exposure
org.jenkins-ci.plugins.workflow:workflow-cps-global-lib☕org.jenkins-ci.plugins.workflow:workflow-cps-global-lib☕org.jenkins-ci.plugins.workflow:workflow-cps-global-libReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the same checkout directories for distinct SCMs for Pipeline libraries, allowing attackers with Item/Configure permission to invoke arbitrary OS commands on the controller through crafted SCM contents.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins.workflow:workflow-cps-global-lib | ≥ 544.vff04fa68714d&&< 561.va | 561.va |
| ☕Maven | org.jenkins-ci.plugins.workflow:workflow-cps-global-lib | ≥ 2.19&&< 2.21.1 | 2.21.1 |
| ☕Maven | org.jenkins-ci.plugins.workflow:workflow-cps-global-lib | all versions | 2.18.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-cps-global-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins.workflow:workflow-cps-global-lib to 561.va or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25174 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-25174 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-25174. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-25174 in your dependencies?
O3 detects CVE-2022-25174 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.