Yet Another Build VisualizerApplication · Jenkins
CVE-2020-2236
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 · uneditedJenkins Yet Another Build Visualizer Plugin 1.11 and earlier does not escape tooltip content, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by users with Run/Update permission.
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 Jenkins Yet Another Build Visualizer Plugin 1.11 and earlier fails to escape tooltip content before rendering it in the UI. An authenticated attacker with Run/Update permission can inject malicious JavaScript into tooltip data fields, which executes in the browsers of other users who view the build visualizations.
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
Yet Another Build VisualizerApplication
<= 1.11CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Yet Another Build Visualizer plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Yet Another Build Visualizer' or 'YABV' to confirm the plugin is present.Affected if The plugin is not installed or has been removed.
-
Determine the installed plugin versionIn the same Installed Plugins list, locate the Yet Another Build Visualizer plugin and note the Version column value displayed.Affected if The installed version is 1.11 or lower (e.g., 1.11, 1.10, 1.9, etc.).
-
Confirm the plugin is enabled and in useCheck that the plugin is not disabled in the plugin manager, and verify that any Jenkins jobs are using the YABV build visualizer view or have the plugin feature active.Affected if The vulnerable version is installed, enabled, and actively rendering build visualizations with tooltips.
A user is affected if the Yet Another Build Visualizer plugin version 1.11 or earlier is installed, enabled, and in use, as this version contains the stored XSS flaw in tooltip rendering.
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 the Yet Another Build Visualizer Plugin to version 1.12 or later which includes proper output encoding for tooltip content. If no patched version is available, disable or remove the plugin until a fix is released.
Fix this in Yet Another Build Visualizer
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2236 — 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-2020-2236 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