First published: Wed Jul 31 2019(Updated: )
Jenkins Maven Release Plug-in Plugin stored credentials unencrypted in its global configuration file `org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.xml` on the Jenkins controller. These credentials could be viewed by users with access to the Jenkins controller file system. Maven Release Plug-in Plugin now stores credentials encrypted.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins M2release | <=0.14.0 | |
Jenkins Maven Release | ||
maven/org.jenkins-ci.plugins.m2release:m2release | <=0.14.0 | 0.15.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10361 is considered a high severity vulnerability due to exposed sensitive credentials.
To fix CVE-2019-10361, update the Jenkins Maven Release Plug-in Plugin to version 0.15.0 or later.
CVE-2019-10361 allows unauthorized users to access unencrypted credentials stored in the Jenkins global configuration file.
Anyone using Jenkins with Maven Release Plug-in Plugin versions up to and including 0.14.0 is affected by CVE-2019-10361.
No, CVE-2019-10361 does not involve remote code execution but rather exposes sensitive information.