CVE-2019-10416 json
Violation Comments to GitLab Plugin has Insufficiently Protected Credentials
published 7y ago modified 4mo ago also GHSA-3p8r-p4q5-mc44 , EUVD-2022-2223
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.jenkins-ci.plugins:violation-comments-to-gitlab 2.29
Is CVE-2019-10416 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
1.07% chance of exploitation in the next 30 days, higher than 65% 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.0 | 4.3 | CVSS:3.0/AV:N/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:violation-comments-to-gitlab | <2.29 |
2.29 |
Affected products
- Jenkins project Jenkins Violation Comments to GitLab Plugin
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
github.com
/jenkinsci/violation-comments-to-gitlab-plugin/commit/e8237a803012bae7773d8bd10fe02e21892be3fe
web
-
jenkins.io
/security/advisory/2019-09-25/#SECURITY-1577
web, vendor-advisory
-
openwall.com
/lists/oss-security/2019/09/25/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10416
advisory
Sources
- CVE List CVE-2019-10416
- GitHub Advisory GHSA-3p8r-p4q5-mc44
- NVD CVE-2019-10416
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.