CVE-2020-2166: Input Validation
First published: Wed Mar 25 2020(Updated: )
Jenkins Pipeline: AWS Steps Plugin 1.40 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerability.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Pipeline\ | <=1.40 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-2166?
CVE-2020-2166 has a high severity due to its potential for remote code execution.
How do I fix CVE-2020-2166?
To fix CVE-2020-2166, upgrade the Jenkins Pipeline: AWS Steps Plugin to version 1.41 or later.
What versions of Jenkins Pipeline: AWS Steps are affected by CVE-2020-2166?
Versions up to and including 1.40 of Jenkins Pipeline: AWS Steps are affected by CVE-2020-2166.
What type of vulnerability is CVE-2020-2166?
CVE-2020-2166 is classified as a remote code execution vulnerability.
What can exploit CVE-2020-2166?
CVE-2020-2166 can be exploited by an attacker able to interact with the vulnerable Jenkins instance, potentially allowing them to execute arbitrary code.
- collector/nvd-index
- collector/nvd-api
- agent/references
- agent/author
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/tags
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/jenkins
- canonical/jenkins pipeline\
- version/jenkins pipeline\/1.40