What is the severity of CVE-2020-2131?

CVE-2020-2131 has a medium severity rating due to the potential exposure of sensitive credentials.

How do I fix CVE-2020-2131?

To fix CVE-2020-2131, upgrade the Jenkins Harvest SCM Plugin to version 0.5.2 or later.

What are the potential impacts of CVE-2020-2131?

The potential impacts of CVE-2020-2131 include unauthorized access to stored passwords for users with Extended Read permission.

Who is affected by CVE-2020-2131?

Users of Jenkins Harvest SCM Plugin version 0.5.1 and earlier are affected by CVE-2020-2131.

Is there a workaround for CVE-2020-2131 if I cannot upgrade?

There is no effective workaround for CVE-2020-2131 other than upgrading to the patched version.

Vulnerability/
CVE-2020-2131

medium

6.5

CWE

522 256

12/2/2020

24/5/2022

4/8/2024

CVE-2020-2131

First published: Wed Feb 12 2020(Updated: )

Jenkins Harvest SCM Plugin 0.5.1 and earlier stores passwords unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.

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

Affected Software	Affected Version	How to fix
Jenkins Harvest Scm	<=0.5.1
maven/org.jenkins-ci.plugins:harvest	<=0.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-2131?
CVE-2020-2131 has a medium severity rating due to the potential exposure of sensitive credentials.
How do I fix CVE-2020-2131?
To fix CVE-2020-2131, upgrade the Jenkins Harvest SCM Plugin to version 0.5.2 or later.
What are the potential impacts of CVE-2020-2131?
The potential impacts of CVE-2020-2131 include unauthorized access to stored passwords for users with Extended Read permission.
Who is affected by CVE-2020-2131?
Users of Jenkins Harvest SCM Plugin version 0.5.1 and earlier are affected by CVE-2020-2131.
Is there a workaround for CVE-2020-2131 if I cannot upgrade?
There is no effective workaround for CVE-2020-2131 other than upgrading to the patched version.

collector/nvd-index
collector/nvd-api
collector/github-advisory-latest
alias/GHSA-qj7p-9hgf-x8j7
alias/CVE-2020-2131
collector/github-advisory
collector/nvd-cve
agent/references
agent/weakness
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/severity
agent/softwarecombine
agent/description
agent/first-publish-date
agent/event
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins harvest scm
version/jenkins harvest scm/0.5.1
package-manager/maven

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-2131?
CVE-2020-2131 has a medium severity rating due to the potential exposure of sensitive credentials.
How do I fix CVE-2020-2131?
To fix CVE-2020-2131, upgrade the Jenkins Harvest SCM Plugin to version 0.5.2 or later.
What are the potential impacts of CVE-2020-2131?
The potential impacts of CVE-2020-2131 include unauthorized access to stored passwords for users with Extended Read permission.
Who is affected by CVE-2020-2131?
Users of Jenkins Harvest SCM Plugin version 0.5.1 and earlier are affected by CVE-2020-2131.
Is there a workaround for CVE-2020-2131 if I cannot upgrade?
There is no effective workaround for CVE-2020-2131 other than upgrading to the patched version.