FitnesseApplication · Jenkins
CVE-2020-2175
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 FitNesse Plugin 1.31 and earlier does not correctly escape report contents before showing them on the Jenkins UI, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by users able to control the XML input files processed by the plugin.
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 Fit Nesse Plugin versions 1.31 and earlier contains a stored cross-site scripting (XSS) vulnerability where report contents are not properly escaped before being rendered in the Jenkins UI. Attackers who can control XML input files processed by the plugin can inject malicious scripts that execute in the browsers of users viewing these reports.
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
FitnesseApplication
<= 1.31CVSS 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 Fit Nesse plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins. Look for 'Fitnesse' or 'Fit Nesse' in the plugin list.Affected if The plugin appears in the installed plugins list.
-
Determine the installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find the Fit Nesse plugin, and note the version number displayed. Alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) within the plugin's .hpi file in $JENKINS_HOME/plugins/.Affected if The version is 1.31 or earlier.
-
Confirm the plugin is enabled and activeIn Jenkins, go to Manage Jenkins > Configure System > look for the Fit Nesse section, or check job configurations to see if Fit Nesse build steps are in use. The vulnerability applies when the plugin processes XML input.Affected if The Fit Nesse plugin is enabled and configured in Jenkins system settings or used in any job configurations.
-
Identify XML input files processed by Fit NesseSearch the Jenkins controller file system for XML files in Fit Nesse test result directories, typically found in $JENKINS_HOME/jobs/<job-name>/fitnesse-results/ or similar paths. Also review job build directories for fitnesse-report.xml or fitnesse-results.xml files.Affected if XML files exist that may contain unsanitized report content processed by the plugin.
The environment is affected if the Fit Nesse plugin version is 1.31 or earlier AND the plugin is enabled and processing XML input files.
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 dataUpdate the Jenkins Fit Nesse Plugin to version 1.32 or later which includes proper output escaping. Alternatively, restrict access to XML input file upload/processing to trusted users only.
Fix this in Fitnesse
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-2175 — 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-2175 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