What is the severity of CVE-2018-1000143?

CVE-2018-1000143 has a high severity rating due to the potential exposure of sensitive GitHub credentials.

How do I fix CVE-2018-1000143?

To fix CVE-2018-1000143, upgrade the Jenkins GitHub Pull Request Builder Plugin to version 1.40.0 or later.

What are the potential risks associated with CVE-2018-1000143?

The risks include unauthorized access to GitHub credentials by an attacker with local file system access.

Where can I find more information about CVE-2018-1000143?

More detailed information about CVE-2018-1000143 can typically be found in security advisories from Jenkins.

Vulnerability/
CVE-2018-1000143

medium

6.7

CWE

200

5/4/2018

3/10/2022

5/8/2024

CVE-2018-1000143: Infoleak

Q: What versions are affected by CVE-2018-1000143?

CVE-2018-1000143 affects Jenkins GitHub Pull Request Builder Plugin versions up to and including 1.39.0.

First published: Thu Apr 05 2018(Updated: )

An exposure of sensitive information vulnerability exists in Jenkins GitHub Pull Request Builder Plugin version 1.39.0 and older in GhprbCause.java that allows an attacker with local file system access to obtain GitHub credentials.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Jenkins Github Pull Request Builder	<=1.39.0

Never miss a vulnerability like this again

Reference Links

https://jenkins.io/security/advisory/2018-03-26/#SECURITY-262

Frequently Asked Questions

What is the severity of CVE-2018-1000143?
CVE-2018-1000143 has a high severity rating due to the potential exposure of sensitive GitHub credentials.
How do I fix CVE-2018-1000143?
To fix CVE-2018-1000143, upgrade the Jenkins GitHub Pull Request Builder Plugin to version 1.40.0 or later.
What versions are affected by CVE-2018-1000143?
CVE-2018-1000143 affects Jenkins GitHub Pull Request Builder Plugin versions up to and including 1.39.0.
What are the potential risks associated with CVE-2018-1000143?
The risks include unauthorized access to GitHub credentials by an attacker with local file system access.
Where can I find more information about CVE-2018-1000143?
More detailed information about CVE-2018-1000143 can typically be found in security advisories from Jenkins.

collector/nvd-index
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/references
agent/tags
agent/author
agent/weakness
agent/event
agent/description
agent/source
vendor/jenkins
canonical/jenkins github pull request builder
version/jenkins github pull request builder/1.39.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-2018-1000143?
CVE-2018-1000143 has a high severity rating due to the potential exposure of sensitive GitHub credentials.
How do I fix CVE-2018-1000143?
To fix CVE-2018-1000143, upgrade the Jenkins GitHub Pull Request Builder Plugin to version 1.40.0 or later.
What versions are affected by CVE-2018-1000143?
CVE-2018-1000143 affects Jenkins GitHub Pull Request Builder Plugin versions up to and including 1.39.0.
What are the potential risks associated with CVE-2018-1000143?
The risks include unauthorized access to GitHub credentials by an attacker with local file system access.
Where can I find more information about CVE-2018-1000143?
More detailed information about CVE-2018-1000143 can typically be found in security advisories from Jenkins.