{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:docker-commons. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-20617 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:docker-commons to 1.18 or later.","what":"CVE-2022-20617 is a high-severity command injection vulnerability in Jenkins Docker Commons Plugin, published on 12 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-20617 and fix it if it is affected.\n\nWhat it is: CVE-2022-20617 is a high-severity command injection vulnerability in Jenkins Docker Commons Plugin, published on 12 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-20617 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:docker-commons (Maven): affected all versions; fixed in 1.18\n- org.jenkins-ci.plugins:docker-commons (Maven): affected all versions; fixed in 1.18\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-20617/ (Markdown: https://insights.sbomify.com/CVE-2022-20617/index.md)","id":"CVE-2022-20617","markdown":"https://insights.sbomify.com/CVE-2022-20617/index.md","name":"CVE-2022-20617","record":{"aliases":["GHSA-jpxj-vgq5-prjc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Docker Plugin","requires_auth":"low_privilege","summary":"Attackers with configure permissions or SCM control can execute OS commands via unsanitized image names in the Jenkins Docker Commons Plugin.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"docker_commons","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2025-08-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-19T16:58:09Z","kind":"github_poc","ref":"https://github.com/shoucheng3/jenkinsci__docker-commons-plugin_CVE-2022-20617_1-17","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"OS command execution vulnerability in Jenkins Docker Commons Plugin","id":"CVE-2022-20617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin","id":"CVE-2022-20618"},"packages":[{"ecosystem":"Maven","fixed":["1.18"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:docker-commons","purl":null,"source":"GHSA-jpxj-vgq5-prjc"},{"ecosystem":"Maven","fixed":["1.18"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:docker-commons","purl":"pkg:maven/org.jenkins-ci.plugins/docker-commons","source":"GHSA-jpxj-vgq5-prjc"}],"prev":{"headline":"Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin","id":"CVE-2022-20616"},"products":["Jenkins Docker Commons Plugin"],"published":"2022-01-12","related":[{"cvss_score":6.5,"headline":"Jenkins Docker Commons Plugin allows any user with Overall/Read permission to get list of valid credentials IDs","id":"CVE-2017-1000094","kev_date_added":null,"published":"2017-10-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Jenkins project"]},"summary":"Attackers with configure permissions or SCM control can execute OS commands via unsanitized image names in the Jenkins Docker Commons Plugin.","url":"https://insights.sbomify.com/CVE-2022-20617/"}