CVE-2019-10459 json
Jenkins Mattermost Notification Plugin contains unencrypted storage of secret token
published 7y ago modified 4mo ago also GHSA-xcj6-4355-2823 , EUVD-2022-5766
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
Jenkins Mattermost Notification Plugin 2.7.0 and earlier stored webhook URLs containing a secret token unencrypted in its global configuration file and 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.
Patch / fix
Is CVE-2019-10459 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.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:mattermost | <2.7.1 |
2.7.1 |
Affected products
- Jenkins project Jenkins Mattermost Notification Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/jenkinsci/mattermost-plugin/commit/c6e509307812d93ba295a35dea95016f007de158
web
-
jenkins.io
/security/advisory/2019-10-23/#SECURITY-1628
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/10/23/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10459
advisory
-
github.com
/jenkinsci/mattermost-plugin
package
Sources
- CVE List CVE-2019-10459
- GitHub Advisory GHSA-xcj6-4355-2823
- NVD CVE-2019-10459
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.