Libvirt SlavesApplication · Jenkins
CVE-2019-10471
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 cross-site request forgery vulnerability in Jenkins Libvirt Slaves Plugin allows attackers 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 confidenceA CSRF vulnerability in Jenkins Libvirt Slaves Plugin allows attackers to trigger connections to attacker-controlled SSH servers using credential IDs, enabling exfiltration of stored Jenkins credentials. The attacker must know valid credential IDs obtained through another means, then tricks an authenticated user into initiating a malicious request.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check if Libvirt Slaves Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Libvirt Slaves' in the list of installed plugins, or check the plugin directory $JENKINS_HOME/plugins for a libvirt-slaves folderAffected if The Libvirt Slaves plugin is present in the Jenkins instance
-
Determine the installed version of Libvirt Slaves PluginIn Manage Jenkins > Manage Plugins > Installed tab, find the Libvirt Slaves plugin and note the version number displayed in the 'Version' columnAffected if The installed version is 1.8.5 or lower
-
Check for configured SSH cloud connectionsNavigate to Manage Jenkins > Manage Nodes > Configure Clouds (or Manage Jenkins > Configure System) and look for any Libvirt cloud configurations that include SSH connection settingsAffected if A Libvirt cloud with SSH credentials is configured and the plugin is vulnerable
-
Review CSRF protection configurationNavigate to Manage Jenkins > Configure Global Security and verify whether 'Enable proxy compatibility' or 'Enable CSRF protection' is enabled under the 'CSRF Protection' sectionAffected if CSRF protection is disabled or not configured (this increases exploitability)
The environment is affected if the Libvirt Slaves plugin version 1.8.5 or lower is installed with SSH cloud configurations, especially if CSRF protection is disabled.
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 dataUpgrade to a patched version of the Libvirt Slaves Plugin and ensure Jenkins master-level CSRF protection is enabled. Revoke any potentially compromised credentials and rotate credential secrets.
Fix this in Libvirt Slaves
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10471 — 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-10471 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