GatlingApplication · Jenkins
CVE-2020-2173
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 Gatling Plugin 1.2.7 and earlier prevents Content-Security-Policy headers from being set for Gatling reports served by the plugin, resulting in an XSS vulnerability exploitable by users able to change report content.
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 Gatling Plugin versions 1.2.7 and earlier prevent Content-Security-Policy headers from being set on Gatling reports served by the plugin. This allows cross-site scripting (XSS) attacks because malicious script content within reports can execute without CSP restrictions. Users with the ability to modify or inject content into Gatling reports can exploit this 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
GatlingApplication
<= 1.2.7CVSS 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 Gatling Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Gatling', or run: java -jar jenkins-cli.jar list-plugins (if CLI is available), or inspect the $JENKINS_HOME/plugins directory for a gatling.hpi or gatling.jpi fileAffected if The Gatling plugin is present in the Jenkins environment
-
Identify the installed Gatling Plugin versionIn the Jenkins UI, click on the Gatling plugin entry in the Installed plugins list to reveal the version number, or examine the plugin manifest file at $JENKINS_HOME/plugins/gatling/META-INF/MANIFEST.MFAffected if The version is 1.2.7 or earlier
-
Determine if Gatling reports are being servedCheck Jenkins job configurations for any jobs that run Gatling load tests and publish reports via the 'Publish Gatling reports' post-build action; inspect the $JENKINS_HOME/jobs/<job-name>/builds/<build-number>/gatling directory for generated report contentAffected if Gatling reports are being generated and served through Jenkins web UI
-
Check for untrusted user access to report contentReview Jenkins project-based matrix authorization or overall matrix permissions to identify users or groups with Job/Build permissions who are not fully trusted; examine whether anonymous or external users have the ability to configure or modify Gatling-related job settingsAffected if Users who are not fully trusted have permissions to create, modify, or configure jobs that generate Gatling reports
You are affected if the Gatling Plugin version is 1.2.7 or earlier AND Gatling reports are being served AND untrusted users have the ability to modify or inject content into those reports.
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 Gatling Plugin to version 1.2.8 or later, which implements proper Content-Security-Policy headers for served reports. If upgrading is not immediately possible, limit report modification permissions to trusted users only.
Fix this in Gatling
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-2173 — 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-2173 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