CVE-2019-10361 json
Jenkins Maven Release Plug-in Plugin stored credentials in plain text
published 7y ago modified 4mo ago also GHSA-vwx8-qpqh-qwm9 , EUVD-2022-5446
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Jenkins Maven Release Plugin 0.14.0 and earlier stored credentials unencrypted on the Jenkins master where they could be viewed by users with access to the master file system.
Patch / fix
- maven org.jenkins-ci.plugins.m2release:m2release 0.15.0
Is CVE-2019-10361 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 3.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins.m2release:m2release | <0.15.0 |
0.15.0 |
Affected products
- Jenkins project Jenkins Maven Release Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/jenkinsci/m2release-plugin/commit/a2e7f2bb82640a9d3641265a19c86ba141a7e79c
web
-
jenkins.io
/security/advisory/2019-07-31/#SECURITY-1435
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/07/31/1
mailing-list, web, third-party-advisory
-
zerodayinitiative.com
/advisories/ZDI-19-835/
third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2019-10361
advisory
Sources
- CVE List CVE-2019-10361
- GitHub Advisory GHSA-vwx8-qpqh-qwm9
- NVD CVE-2019-10361
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.