CVE-2022-20617: OS Command Injection

Published Jan 12, 2022
·
Updated

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 Software

2 affected componentsFixes available
maven/org.jenkins-ci.plugins:docker-commons<1.18
1.18
Jenkins Docker Commons Jenkins<=1.17

Event History

Jan 12, 2022
CVE Published
via MITRE·07:05 PM
Data Sourced
via MITRE·07:05 PM
Description
Jan 13, 2022
Advisory Published
12:01 AM

Frequently Asked Questions

1

What is the severity of CVE-2022-20617?

CVE-2022-20617 has a high severity level due to its capability for OS command execution.

2

How do I fix CVE-2022-20617?

To fix CVE-2022-20617, upgrade the Jenkins Docker Commons Plugin to version 1.18 or later.

3

Who is affected by CVE-2022-20617?

Users with Item/Configure permission or those who can control the contents of a job's SCM repository are potentially at risk.

4

What versions of Jenkins Docker Commons are vulnerable to CVE-2022-20617?

Jenkins Docker Commons Plugin versions 1.17 and earlier are vulnerable to CVE-2022-20617.

5

What types of attacks can exploit CVE-2022-20617?

CVE-2022-20617 can be exploited to execute arbitrary OS commands in a Jenkins environment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203