Libvirt SlavesApplication · Jenkins
CVE-2019-10472
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA missing permission check in Jenkins Libvirt Slaves Plugin allows attackers with Overall/Read permission to connect to an attacker-specified SSH server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMissing permission check in Jenkins Libvirt Slaves Plugin allows attackers with Overall/Read permission to enumerate and use stored SSH credentials to connect to attacker-controlled SSH servers. This is an Insecure Direct Object Reference (IDOR) combined with insufficient authorization, enabling credential theft via credential ID manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Libvirt SlavesApplication
<= 1.8.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Libvirt Slaves Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Libvirt Slaves' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Installed plugins list, locate the Libvirt Slaves plugin and note the Version column. Compare this version number to 1.8.5Affected if The version is 1.8.5 or lower
-
Identify stored SSH credentialsNavigate to Credentials > System > Global credentials and look for any SSH credentials entries. Note the credential IDs present in the storeAffected if There are SSH credentials stored with known IDs
-
Verify Overall/Read permission is grantedNavigate to Manage Jenkins > Manage Users and review which users have Overall/Read permission, or check Matrix-based security settings under Manage Jenkins > Configure Global SecurityAffected if Users beyond trusted administrators have Overall/Read permission
-
Test credential ID enumerationAttempt to access credential details via Libvirt Slaves plugin API endpoints using guessed credential IDs while authenticated with only Overall/Read permissionAffected if A user with only Overall/Read permission can access or reference stored SSH credential IDs
A user is affected if the Libvirt Slaves Plugin version is 1.8.5 or lower AND SSH credentials are stored in Jenkins AND users with Overall/Read permission can access the credential IDs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the security fix from the plugin's release notes - upgrade to the patched version of Libvirt Slaves Plugin. Additionally, restrict Overall/Read permission to only trusted users and audit credential storage.
Fix this in Libvirt Slaves
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10472 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data