FindbugsApplication · Jenkins
CVE-2020-2317
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 FindBugs Plugin 5.0.0 and earlier does not escape the annotation message in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide report files to Jenkins FindBugs 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 confidenceJenkins FindBugs Plugin versions 5.0.0 and earlier fails to properly escape annotation messages displayed in tooltips, allowing stored XSS injection. Attackers who can supply report files to the plugin's post-build step can embed malicious JavaScript that executes when users view the affected tooltips.
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
FindbugsApplication
<= 5.0.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
- 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.
-
Confirm FindBugs plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for FindBugs in the list of installed pluginsAffected if FindBugs plugin appears in the installed plugins list
-
Check installed FindBugs plugin versionIn the installed plugins list, locate FindBugs and note the version number displayed. Compare this version to the affected range: 5.0.0 and earlierAffected if The installed version is 5.0.0 or any version lower than 5.0.0
-
Identify if FindBugs post-build step is configuredOpen a Jenkins job configuration that uses FindBugs. Look under Post-Build Actions for 'Publish FindBugs analysis report' or similar FindBugs-related post-build stepsAffected if A FindBugs post-build action is configured to publish analysis reports
-
Determine if report files can be supplied by untrusted usersReview job configuration and overall Jenkins permissions to check whether users without admin privileges can trigger builds or supply custom report files to the FindBugs post-build stepAffected if Untrusted or low-privilege users can supply or influence the report files processed by the FindBugs plugin
A user is affected if the FindBugs plugin is installed at version 5.0.0 or earlier AND a FindBugs post-build step is configured AND untrusted users can supply report files to that step.
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 version newer than 5.0.0 which includes proper output escaping. If upgrade is not immediately feasible, restrict or validate report file inputs to the FindBugs post-build step.
Fix this in Findbugs
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2317 — 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-2317 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