First published: Wed Sep 25 2019(Updated: )
Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or 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-10416 has a severity rating of medium due to the exposure of unencrypted credentials.
To mitigate CVE-2019-10416, upgrade the Violation Comments to GitLab Plugin to version 2.29 or later.
CVE-2019-10416 affects the Jenkins Violation Comments to GitLab Plugin versions 2.28 and earlier.
Users with Extended Read permission or access to the Jenkins master file system can view the credentials exposed by CVE-2019-10416.
CVE-2019-10416 compromises API tokens that are stored unencrypted in job config.xml files.