Copy Data To WorkspaceApplication · Jenkins
CVE-2020-2275
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 Copy data to workspace Plugin 1.0 and earlier does not limit which directories can be copied from the Jenkins controller to job workspaces, allowing attackers with Job/Configure permission to read arbitrary files on the Jenkins controller.
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 Copy data to workspace Plugin versions 1.0 and earlier lacks proper directory path validation, allowing attackers with Job/Configure permission to specify arbitrary paths on the Jenkins controller filesystem and copy them to job workspaces. This constitutes a path traversal vulnerability enabling unauthorized file disclosure.
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
Copy Data To WorkspaceApplication
<= 1.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Copy Data To Workspace plugin is installedCheck for the plugin in $JENKINS_HOME/plugins/ directory for a folder or .jpi/.hpi file named 'copy-data-to-workspace'Affected if Plugin files exist in the Jenkins plugins directory
-
Determine the installed plugin versionOpen the plugin's MANIFEST.MF file in the plugin directory and read the 'Implementation-Version' or 'Plugin-Version' attribute, or use the Jenkins UI at Manage Jenkins > Manage Plugins > Installed tab to find the versionAffected if Version is 1.0 or earlier
-
Confirm plugin is enabledIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and verify the Copy Data To Workspace plugin shows as 'Enabled' or check the $JENKINS_HOME/plugins/copy-data-to-workspace.jpi.disabled file does not existAffected if Plugin is enabled and active in Jenkins
-
Verify Jenkins user permissions configurationReview Jenkins authorization matrix at Manage Jenkins > Configure Global Security to identify which users or groups have Job/Configure or Job/Build permissionsAffected if Users with Job/Configure permission exist and the vulnerable plugin is installed
Environment is affected if the Copy Data To Workspace plugin is installed and enabled with version 1.0 or earlier, allowing any user with Job/Configure permission to perform path traversal attacks.
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 Copy data to workspace Plugin to a patched version that implements proper directory path restrictions and validates that only allowed directories can be accessed for copying.
Fix this in Copy Data To Workspace
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2275 — 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-2275 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