What is the severity of CVE-2020-2118?

CVE-2020-2118 is classified as a medium severity vulnerability due to the potential exposure of sensitive credential information.

How do I fix CVE-2020-2118?

To fix CVE-2020-2118, upgrade the Pipeline GitHub Notify Step Plugin to version 1.0.5 or later.

What kind of access is required to exploit CVE-2020-2118?

Exploitation of CVE-2020-2118 requires users to have Overall/Read access to Jenkins.

What does CVE-2020-2118 allow attackers to do?

CVE-2020-2118 allows attackers to enumerate credentials IDs of stored credentials in Jenkins.

Which versions of Jenkins are affected by CVE-2020-2118?

CVE-2020-2118 affects Jenkins Pipeline GitHub Notify Step Plugin versions 1.0.4 and earlier.

Vulnerability/
CVE-2020-2118

medium

4.3

CWE

276 285

12/2/2020

24/5/2022

4/8/2024

CVE-2020-2118

First published: Wed Feb 12 2020(Updated: )

A missing permission check in Jenkins Pipeline GitHub Notify Step Plugin 1.0.4 and earlier in form-related methods allowed users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins.

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

Affected Software	Affected Version	How to fix
maven/org.jenkins-ci.plugins:pipeline-build-step	<1.0.5	1.0.5
Jenkins Pipeline Github Notify Step	<=1.0.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-2118?
CVE-2020-2118 is classified as a medium severity vulnerability due to the potential exposure of sensitive credential information.
How do I fix CVE-2020-2118?
To fix CVE-2020-2118, upgrade the Pipeline GitHub Notify Step Plugin to version 1.0.5 or later.
What kind of access is required to exploit CVE-2020-2118?
Exploitation of CVE-2020-2118 requires users to have Overall/Read access to Jenkins.
What does CVE-2020-2118 allow attackers to do?
CVE-2020-2118 allows attackers to enumerate credentials IDs of stored credentials in Jenkins.
Which versions of Jenkins are affected by CVE-2020-2118?
CVE-2020-2118 affects Jenkins Pipeline GitHub Notify Step Plugin versions 1.0.4 and earlier.

collector/nvd-index
collector/nvd-api
collector/github-advisory-latest
alias/GHSA-8p4m-62gp-33j4
alias/CVE-2020-2118
collector/github-advisory
collector/nvd-cve
agent/weakness
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/references
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins pipeline github notify step
version/jenkins pipeline github notify step/1.0.4
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-2118?
CVE-2020-2118 is classified as a medium severity vulnerability due to the potential exposure of sensitive credential information.
How do I fix CVE-2020-2118?
To fix CVE-2020-2118, upgrade the Pipeline GitHub Notify Step Plugin to version 1.0.5 or later.
What kind of access is required to exploit CVE-2020-2118?
Exploitation of CVE-2020-2118 requires users to have Overall/Read access to Jenkins.
What does CVE-2020-2118 allow attackers to do?
CVE-2020-2118 allows attackers to enumerate credentials IDs of stored credentials in Jenkins.
Which versions of Jenkins are affected by CVE-2020-2118?
CVE-2020-2118 affects Jenkins Pipeline GitHub Notify Step Plugin versions 1.0.4 and earlier.