Sonargraph IntegrationApplication · Jenkins
CVE-2020-2201
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 Sonargraph Integration Plugin 3.0.0 and earlier does not escape the file path for the Log file field form validation, resulting in a stored cross-site scripting vulnerability.
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 Sonargraph Integration Plugin version 3.0.0 and earlier contains a stored cross-site scripting vulnerability in the 'Log file' field form validation. The plugin fails to properly escape user-supplied file path input before rendering it in the validation response, allowing malicious JavaScript to be executed in the browsers of users who view the affected form validation output.
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
Sonargraph IntegrationApplication
<= 3.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.
-
Verify Sonargraph Integration plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Sonargraph Integration' in the list of installed plugins.Affected if The plugin appears in the installed plugins list.
-
Check installed plugin versionIn the Installed Plugins page, locate the Sonargraph Integration plugin and note the Version column. Alternatively, check the $JENKINS_HOME/plugins/sonargraph-integration/WEB-INF/manifest.mf file for the Plugin-Version attribute.Affected if The version is 3.0.0 or lower.
-
Confirm the Log file field exists in job configurationsCreate or edit a freestyle or pipeline job configured to use Sonargraph Integration build steps. Locate the 'Log file' or 'Log file path' input field within the Sonargraph build configuration section.Affected if The 'Log file' input field is present and available for configuration in the job.
-
Check for existing job configurations using Log file fieldReview existing Jenkins jobs that use Sonargraph Integration and check if any have a value set in the 'Log file' or 'Log file path' parameter. This can be done by viewing job configuration XML files in $JENKINS_HOME/jobs/<jobname>/config.xml or via Jenkins API.Affected if Any job configuration contains a non-empty value in the Sonargraph Log file parameter.
If the Sonargraph Integration plugin version is 3.0.0 or earlier AND the Log file field is present or has been used in any job configuration, the environment is vulnerable to stored XSS via this CVE.
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 Sonargraph Integration Plugin to version 3.1.0 or later which implements proper escaping of the file path field. Until patched, restrict access to trusted users only.
Fix this in Sonargraph Integration
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-2201 — 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-2201 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