What is the severity of CVE-2020-2159?

CVE-2020-2159 is classified as a critical vulnerability due to the potential for arbitrary OS command execution.

How do I fix CVE-2020-2159?

To fix CVE-2020-2159, upgrade to Jenkins CryptoMove Plugin version 0.1.34 or later.

Who is affected by CVE-2020-2159?

Any Jenkins instance with CryptoMove Plugin versions 0.1.33 and earlier that allows Job/Configure access is affected.

What are the implications of CVE-2020-2159?

The implications of CVE-2020-2159 include the risk of attackers executing arbitrary commands with the privileges of the Jenkins master.

Is there a workaround for CVE-2020-2159?

The recommended workaround for CVE-2020-2159 is to restrict Job/Configure access until the plugin is updated.

Vulnerability/
CVE-2020-2159

critical

CWE

9/3/2020

4/8/2024

CVE-2020-2159: OS Command Injection

First published: Mon Mar 09 2020(Updated: )

Jenkins CryptoMove Plugin 0.1.33 and earlier allows attackers with Job/Configure access to execute arbitrary OS commands on the Jenkins master as the OS user account running Jenkins.

Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Cryptomove	<=0.1.33

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-2159?
CVE-2020-2159 is classified as a critical vulnerability due to the potential for arbitrary OS command execution.
How do I fix CVE-2020-2159?
To fix CVE-2020-2159, upgrade to Jenkins CryptoMove Plugin version 0.1.34 or later.
Who is affected by CVE-2020-2159?
Any Jenkins instance with CryptoMove Plugin versions 0.1.33 and earlier that allows Job/Configure access is affected.
What are the implications of CVE-2020-2159?
The implications of CVE-2020-2159 include the risk of attackers executing arbitrary commands with the privileges of the Jenkins master.
Is there a workaround for CVE-2020-2159?
The recommended workaround for CVE-2020-2159 is to restrict Job/Configure access until the plugin is updated.

collector/security-tracker-debian
collector/nvd-index
collector/nvd-api
agent/author
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/last-modified-date
agent/weakness
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/jenkins
canonical/jenkins cryptomove
version/jenkins cryptomove/0.1.33

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2020-2159?
CVE-2020-2159 is classified as a critical vulnerability due to the potential for arbitrary OS command execution.
How do I fix CVE-2020-2159?
To fix CVE-2020-2159, upgrade to Jenkins CryptoMove Plugin version 0.1.34 or later.
Who is affected by CVE-2020-2159?
Any Jenkins instance with CryptoMove Plugin versions 0.1.33 and earlier that allows Job/Configure access is affected.
What are the implications of CVE-2020-2159?
The implications of CVE-2020-2159 include the risk of attackers executing arbitrary commands with the privileges of the Jenkins master.
Is there a workaround for CVE-2020-2159?
The recommended workaround for CVE-2020-2159 is to restrict Job/Configure access until the plugin is updated.