CVE-2019-10473 json
Jenkins Libvirt Slaves Plugin vlnerable to Credential Enumeration
published 7y ago modified 4mo ago also GHSA-8j3m-j6x6-cp5v , EUVD-2022-3190
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
A missing permission check in Jenkins Libvirt Slaves Plugin in form-related methods allowed users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins.
Patch / fix
- maven org.jenkins-ci.plugins:libvirt-slave 1.8.6
Is CVE-2019-10473 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.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/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:libvirt-slave | <1.8.6 |
1.8.6 |
Affected products
- Jenkins project Jenkins Libvirt Slaves Plugin
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
github.com
/jenkinsci/libvirt-slave-plugin/commit/c671d68f9498414a735913c9372ede8b4791bfee
web
- jenkins.io /security/advisory/2019-10-23/#SECURITY-1014%20%282%29
-
openwall.com
/lists/oss-security/2019/10/23/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10473
advisory
-
github.com
/jenkinsci/libvirt-slave-plugin
package
-
github.com
/jenkinsci/libvirt-slave-plugin/releases
web
-
jenkins.io
/security/advisory/2019-10-23/#SECURITY-1014%20(2)
web
Sources
- CVE List CVE-2019-10473
- GitHub Advisory GHSA-8j3m-j6x6-cp5v
- NVD CVE-2019-10473
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.