What is the severity of CVE-2019-10429?

CVE-2019-10429 is considered to be a high severity vulnerability due to the potential exposure of sensitive credentials.

How do I fix CVE-2019-10429?

To fix CVE-2019-10429, upgrade the Jenkins GitLab Logo Plugin to version 1.0.4 or higher.

What are the consequences of CVE-2019-10429?

The consequences of CVE-2019-10429 include unauthorized access to sensitive credentials stored unencrypted on the Jenkins master.

What versions of the GitLab Logo Plugin are affected by CVE-2019-10429?

CVE-2019-10429 affects GitLab Logo Plugin versions up to and including 1.0.3.

Who is at risk from CVE-2019-10429?

Users with access to the Jenkins master file system are at risk from CVE-2019-10429 as they can view the stored unencrypted credentials.

Vulnerability/
CVE-2019-10429

medium

5.5

CWE

522 256

25/9/2019

24/5/2022

4/8/2024

CVE-2019-10429

First published: Wed Sep 25 2019(Updated: )

Jenkins GitLab Logo Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with 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
maven/org.jenkins-ci.plugins:gitlab-logo	<1.0.4	1.0.4
Jenkins GitLab	<=1.0.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-10429?
CVE-2019-10429 is considered to be a high severity vulnerability due to the potential exposure of sensitive credentials.
How do I fix CVE-2019-10429?
To fix CVE-2019-10429, upgrade the Jenkins GitLab Logo Plugin to version 1.0.4 or higher.
What are the consequences of CVE-2019-10429?
The consequences of CVE-2019-10429 include unauthorized access to sensitive credentials stored unencrypted on the Jenkins master.
What versions of the GitLab Logo Plugin are affected by CVE-2019-10429?
CVE-2019-10429 affects GitLab Logo Plugin versions up to and including 1.0.3.
Who is at risk from CVE-2019-10429?
Users with access to the Jenkins master file system are at risk from CVE-2019-10429 as they can view the stored unencrypted credentials.

collector/github-advisory-latest
alias/GHSA-22rj-q66g-2jg3
alias/CVE-2019-10429
collector/github-advisory
agent/weakness
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/references
agent/last-modified-date
agent/first-publish-date
agent/description
agent/event
agent/trending
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
collector/nvd-cve
package-manager/maven
vendor/jenkins
canonical/jenkins gitlab
version/jenkins gitlab/1.0.3

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-2019-10429?
CVE-2019-10429 is considered to be a high severity vulnerability due to the potential exposure of sensitive credentials.
How do I fix CVE-2019-10429?
To fix CVE-2019-10429, upgrade the Jenkins GitLab Logo Plugin to version 1.0.4 or higher.
What are the consequences of CVE-2019-10429?
The consequences of CVE-2019-10429 include unauthorized access to sensitive credentials stored unencrypted on the Jenkins master.
What versions of the GitLab Logo Plugin are affected by CVE-2019-10429?
CVE-2019-10429 affects GitLab Logo Plugin versions up to and including 1.0.3.
Who is at risk from CVE-2019-10429?
Users with access to the Jenkins master file system are at risk from CVE-2019-10429 as they can view the stored unencrypted credentials.