Zap PipelineApplication · Jenkins
CVE-2020-2214
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 ZAP Pipeline Plugin 1.9 and earlier programmatically disables Content-Security-Policy protection for user-generated content in workspaces, archived artifacts, etc. that Jenkins offers for download.
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 · moderate confidenceThe Jenkins ZAP Pipeline Plugin version 1.9 and earlier disables Content-Security-Policy protection headers that Jenkins normally applies to user-generated content served for download, including workspace files and archived artifacts. This removes a security safeguard that helps prevent XSS attacks when users download or view content that may contain malicious scripts.
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
Zap PipelineApplication
<= 1.9CVSS 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 Jenkins ZAP Pipeline Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use: jenkins-cli.jar who-am-i or API endpoint /pluginManager/api/json?tree=plugins[shortName,version] to list installed plugins. Look for 'zap-pipeline' or 'ZAP Pipeline' in the plugin list.Affected if The plugin named 'zap-pipeline' or 'ZAP Pipeline' appears in the installed plugins list
-
Check the installed version numberIn the Manage Plugins > Installed view, locate the ZAP Pipeline Plugin and read the Version column. If using CLI/API, the version field is returned in the plugins JSON response.Affected if The version number is 1.9 or lower (for example: 1.9, 1.8, 1.7, etc.)
-
Confirm CSP headers are missing from workspace file downloadsTrigger a build that produces workspace files, then attempt to download a file from the workspace (JENKINS_URL/job/JOBNAME/ws/FILENAME). Use curl -I or browser DevTools to inspect the HTTP response headers for Content-Security-Policy. Alternatively, use Jenkins API: curl -s -D - -o /dev/null JENKINS_URL/job/JOBNAME/ws/yourfileAffected if The Content-Security-Policy header is absent from the HTTP response when downloading workspace files
-
Confirm CSP headers are missing from archived artifact downloadsLocate a build with archived artifacts, then download an artifact (JENKINS_URL/job/JOBName/BUILD_NUMBER/artifact/PATH). Inspect the response headers for Content-Security-Policy as in step 3.Affected if The Content-Security-Policy header is absent from the HTTP response when downloading archived artifacts
The environment is affected if the ZAP Pipeline Plugin version is 1.9 or lower AND CSP headers are missing from workspace file and artifact downloads.
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 ZAP Pipeline Plugin to a version newer than 1.9. If immediate upgrade is not possible, consider restricting access to workspace downloads and archived artifacts or implementing additional controls on served content.
Fix this in Zap Pipeline
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2214 — 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-2214 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