What is the severity of CVE-2020-2158?

CVE-2020-2158 is classified as a critical vulnerability due to its potential for remote code execution.

How do I fix CVE-2020-2158?

To fix CVE-2020-2158, you should upgrade to Jenkins Literate Plugin version 1.1 or later.

What causes the vulnerability in CVE-2020-2158?

CVE-2020-2158 is caused by the YAML parser in the Jenkins Literate Plugin not being configured properly, allowing the instantiation of arbitrary types.

Is CVE-2020-2158 exploitable remotely?

Yes, CVE-2020-2158 is exploitable remotely, which can lead to unauthorized execution of code on affected systems.

What software is affected by CVE-2020-2158?

CVE-2020-2158 affects the Jenkins Literate Plugin version 1.0 and earlier.

Vulnerability/
CVE-2020-2158

high

8.8

CWE

502

9/3/2020

4/8/2024

CVE-2020-2158

First published: Mon Mar 09 2020(Updated: )

Jenkins Literate Plugin 1.0 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 Literate	<=1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-2158?
CVE-2020-2158 is classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2020-2158?
To fix CVE-2020-2158, you should upgrade to Jenkins Literate Plugin version 1.1 or later.
What causes the vulnerability in CVE-2020-2158?
CVE-2020-2158 is caused by the YAML parser in the Jenkins Literate Plugin not being configured properly, allowing the instantiation of arbitrary types.
Is CVE-2020-2158 exploitable remotely?
Yes, CVE-2020-2158 is exploitable remotely, which can lead to unauthorized execution of code on affected systems.
What software is affected by CVE-2020-2158?
CVE-2020-2158 affects the Jenkins Literate Plugin version 1.0 and earlier.

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

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-2158?
CVE-2020-2158 is classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2020-2158?
To fix CVE-2020-2158, you should upgrade to Jenkins Literate Plugin version 1.1 or later.
What causes the vulnerability in CVE-2020-2158?
CVE-2020-2158 is caused by the YAML parser in the Jenkins Literate Plugin not being configured properly, allowing the instantiation of arbitrary types.
Is CVE-2020-2158 exploitable remotely?
Yes, CVE-2020-2158 is exploitable remotely, which can lead to unauthorized execution of code on affected systems.
What software is affected by CVE-2020-2158?
CVE-2020-2158 affects the Jenkins Literate Plugin version 1.0 and earlier.