Xl TestviewApplication · Jenkins
CVE-2019-10386
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 XL TestView Plugin 1.2.0 and earlier in XLTestView.XLTestDescriptor#doTestConnection allows users with Overall/Read access to connect to an attacker-specified URL 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 confidenceThe XL TestView Plugin for Jenkins versions 1.2.0 and earlier lacks Cross-Site Request Forgery (CSRF) protection on the XLTestView.XLTestDescriptor#doTestConnection endpoint. This allows attackers to craft malicious requests that, when triggered by an authenticated user with Overall/Read access, force the Jenkins server to connect to attacker-controlled URLs with attacker-specified credential IDs, enabling credential harvesting from Jenkins' credential store.
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
Xl TestviewApplication
<= 1.2.0CVSS 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.
-
Confirm XL TestView plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-pluginsAffected if XL TestView appears in the list of installed plugins
-
Identify the installed version of XL TestViewIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate XL TestView and note the Version column; or check the plugin's manifest file (plugins/xl-testview-plugin/META-INF/MANIFEST.MF)Affected if A version number is displayed for the plugin
-
Compare version against affected rangeIf version 1.2.0 or earlier is shown, the plugin is within the vulnerable range; versions 1.2.1 and later include the CSRF fixAffected if Installed version is 1.2.0 or lower
-
Verify plugin is active and exposedCheck Jenkins > Manage Jenkins > Manage Plugins > Installed tab to confirm the plugin status is 'Enabled' and there are no pending restarts; also verify the plugin's API endpoint is reachableAffected if Plugin is enabled and the doTestConnection endpoint is accessible
If XL TestView plugin version 1.2.0 or earlier is installed and enabled, the environment is vulnerable to CVE-2019-10386 and could allow CSRF-based credential harvesting.
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 XL TestView Plugin to version 1.2.1 or later which includes CSRF protection (crumb) on the vulnerable endpoint. If an upgrade is unavailable, disable or remove the plugin until a patch is released.
Fix this in Xl Testview
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10386 — 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-10386 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