Coverage\/complexity Scatter PlotApplication · Jenkins
CVE-2020-2265
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 Coverage/Complexity Scatter Plot Plugin 1.1.1 and earlier does not escape the method information in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide report files to the plugin's post-build step.
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 Coverage/Complexity Scatter Plot Plugin versions 1.1.1 and earlier fails to properly escape or encode method information when rendering tooltips. This allows attackers who can supply specially crafted report files to the plugin's post-build step to inject malicious JavaScript code that executes in the browsers of users viewing the tooltip data—a stored cross-site scripting (XSS) vulnerability.
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
Coverage\/complexity Scatter PlotApplication
<= 1.1.1CVSS 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 the Coverage/Complexity Scatter Plot Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Coverage/Complexity Scatter Plot' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the plugin list, locate the Coverage/Complexity Scatter Plot entry and note the Version column. Alternatively, access Jenkins > Manage Jenkins > Manage Plugins > Advanced > and find the plugin in the 'Plug-in Installation History' or check the plugin's WEB-INF/pom.xml if accessible on the controller filesystemAffected if The version is 1.1.1 or earlier (versions up to and including 1.1.1 are affected)
-
Identify if the plugin post-build step is in useReview configured jobs: go to each job > Configure > scroll to 'Post-build Actions' and look for 'Record Coverage/Complexity Scatter Plot' or similar coverage recording actionAffected if The post-build step is configured and processes report files
-
Determine who can trigger jobs or upload report filesReview job configuration under 'Build Triggers' and check project-based matrix authorization settings or who has Job/Build permissions. Also check if any scripts or pipelines accept external report file inputsAffected if Untrusted or anonymous users have the ability to supply coverage or report files to jobs using this plugin
You are affected if the Coverage/Complexity Scatter Plot Plugin version 1.1.1 or earlier is installed AND its post-build step is configured to process report files, especially in jobs accessible to untrusted users.
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 Jenkins Coverage/Complexity Scatter Plot Plugin to version 1.2.0 or later which includes proper output encoding. If upgrade is not immediately possible, restrict who can upload report files to job post-build steps and sanitize any externally-sourced coverage reports before processing.
Fix this in Coverage\/complexity Scatter Plot
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2265 — 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-2265 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