CVE-2019-10473 is a medium-severity (CVSS 4.3) Incorrect Default Permissions vulnerability in org.jenkins-ci.plugins:libvirt-slave. A fix is available for org.jenkins-ci.plugins:libvirt-slave — see the affected versions and patch details below.
Jenkins Libvirt Slaves Plugin vlnerable to Credential Enumeration
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:libvirt-slaveReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:libvirt-slave | all versions | 1.8.6org.jenkins-ci.plugins:libvirt-slave:1.8.6 |
Affected Products
libvirt slavesjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:libvirt-slave, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:libvirt-slave to 1.8.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10473 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2019-10473 in your dependencies?
Find it across Maven, including transitive dependencies.