Static Analysis UtilitiesApplication · Jenkins
CVE-2020-2316
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 Static Analysis Utilities Plugin 1.96 and earlier does not escape the annotation message in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure 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 Static Analysis Utilities Plugin versions 1.96 and earlier fails to properly escape annotation messages when rendering them in tooltips. An attacker with Job/Configure permission can inject malicious JavaScript into an annotation message, which is then stored and executed in the browsers of other users who 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
Static Analysis UtilitiesApplication
<= 1.96CVSS 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 Jenkins Static Analysis Utilities Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Static Analysis Utilities' or check the plugin directory $JENKINS_HOME/plugins for the static-analysis-utilities folderAffected if The plugin folder exists in the plugins directory or the plugin appears in the installed list
-
Check the installed plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find Static Analysis Utilities, and note the version number. Alternatively, inspect the $JENKINS_HOME/plugins/static-analysis-utilations/META-INF/MANIFEST.MF file for the Plugin-Version attributeAffected if The version is 1.96 or earlier (any version listed as 1.96 or lower)
-
Identify users with Job/Configure permissionIn Jenkins, go to Manage Jenkins > Manage and Assign Users and review which users have Job/Configure permissions, or use the Jenkins script console with: Jenkins.instance.getAllItems().each { println it.class.simpleName + ': ' + it.hasPermission(Jenkins.CONFIGURE) } to list configure permissionsAffected if Any untrusted user has Job/Configure permission (this permission level is required to inject the malicious annotation)
-
Verify if static analysis results with annotations are being displayedCheck any Jenkins jobs that use static analysis tools (such as Checkstyle, PMD, FindBugs, etc.) and view job pages to see if annotation markers appear in build artifacts or console outputAffected if Static analysis results with clickable annotations are visible in job pages or build artifacts (this is where the XSS would execute)
If the Static Analysis Utilities plugin version is 1.96 or earlier AND static analysis annotations are displayed AND untrusted users have Job/Configure permission, the environment is vulnerable to CVE-2020-2316.
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 Jenkins Static Analysis Utilities Plugin to version 1.97 or later, which includes proper escaping of annotation messages in tooltips. Until then, restrict Job/Configure permission to trusted users only.
Fix this in Static Analysis Utilities
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2316 — 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-2316 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