CVE-2019-10429: Medium severity jenkins gitlab vulnerability
Published 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.
Affected Software
2 affected componentsFixes available
maven/org.jenkins-ci.plugins:gitlab-logo<1.0.4
1.0.4
Jenkins Gitlab Logo Jenkins<=1.0.3
Event History
Sep 25, 2019
CVE Published
via MITRE·03:05 PM
Data Sourced
via MITRE·03:05 PM
Description
May 24, 2022
Advisory Published
10:00 PM
Frequently Asked Questions
1
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.
2
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.
3
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.
4
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.
5
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.