First published: Wed Sep 25 2019(Updated: )
Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could 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 |
---|---|---|
Jenkins Violation Comments To Gitlab | <=2.28 | |
maven/org.jenkins-ci.plugins:violation-comments-to-gitlab | <2.29 | 2.29 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10415 is considered a medium severity vulnerability due to unencrypted storage of sensitive credentials.
To fix CVE-2019-10415, upgrade the Jenkins Violation Comments to GitLab Plugin to version 2.29 or later.
CVE-2019-10415 affects the stored API tokens and credentials that are kept unencrypted in the plugin's configuration.
Users with access to the Jenkins master file system are impacted by CVE-2019-10415 as they can view unencrypted credentials.
Versions 2.28 and earlier of the Jenkins Violation Comments to GitLab Plugin are vulnerable to CVE-2019-10415.