CVE-2022-20617 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in org.jenkins-ci.plugins:docker-commons. A fix is available for org.jenkins-ci.plugins:docker-commons — see the affected versions and patch details below.
OS command execution vulnerability in Jenkins Docker Commons Plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-20617 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.plugins:docker-commonsReal-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 Docker Commons Plugin 1.17 and earlier does not sanitize the name of an image or a tag, resulting in an OS command execution vulnerability exploitable by attackers with Item/Configure permission or able to control the contents of a previously configured job's SCM repository.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:docker-commons | all versions | 1.18org.jenkins-ci.plugins:docker-commons:1.18 |
Affected Products
docker commonsjenkinsDetection & 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:docker-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:docker-commons to 1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20617 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-2-plugins-0:3.11.1644412543-1.el7 | RHSA-2022:0555 |
| Red Hat OpenShift Container Platform 4.10 | jenkins-2-plugins-0:4.10.1643404185-1.el8 | RHSA-2022:0055 |
| Red Hat OpenShift Container Platform 4.6 | jenkins-2-plugins-0:4.6.1643965689-1.el8 | RHSA-2022:0565 |
| Red Hat OpenShift Container Platform 4.7 | jenkins-2-plugins-0:4.7.1643883495-1.el8 | RHSA-2022:0491 |
| Red Hat OpenShift Container Platform 4.8 | jenkins-2-plugins-0:4.8.1643649345-1.el8 | RHSA-2022:0483 |
| Red Hat OpenShift Container Platform 4.9 | jenkins-2-plugins-0:4.9.1643389956-1.el8 | RHSA-2022:0339 |
Frequently Asked Questions
Is CVE-2022-20617 in your dependencies?
Find it across Maven, including transitive dependencies.