CoberturaApplication · Jenkins
CVE-2020-2139
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 · uneditedAn arbitrary file write vulnerability in Jenkins Cobertura Plugin 1.15 and earlier allows attackers able to control the coverage report file contents to overwrite any file on the Jenkins master file system.
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 Cobertura Plugin versions 1.15 and earlier contains an arbitrary file write vulnerability. Attackers with the ability to control coverage report file contents can exploit the plugin's processing of these reports to overwrite any file on the Jenkins master file system, leading to potential code execution or denial of service.
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
CoberturaApplication
<= 1.15CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Cobertura Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Cobertura', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep CoberturaAffected if The Cobertura plugin appears in the installed plugins list
-
Check the installed Cobertura Plugin versionIn Manage Plugins > Installed, locate Cobertura and note the Version column, or check the plugin's pom.xml/manifest if accessible on the filesystemAffected if The installed version is 1.15 or lower
-
Confirm the plugin is enabledIn Manage Plugins > Installed, verify the Cobertura plugin shows as 'Enabled' and not grayed out, or check <jenkins_home>/plugins/cobertura/META-INF/MANIFEST.MF existsAffected if The plugin is enabled and actively loaded by Jenkins
-
Identify who has access to coverage report uploadNavigate to the job configuration that uses Cobertura publishing, check the 'Post-build Actions' for 'Publish Cobertura Coverage Report', and review job-level or matrix-based permissions for who can configure or trigger those jobsAffected if Users other than trusted administrators can configure jobs that publish Cobertura coverage reports
If the Cobertura Plugin is installed at version 1.15 or lower and is enabled, and untrusted users can access coverage report upload configurations, the environment is vulnerable to CVE-2020-2139.
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 Cobertura Plugin to a version newer than 1.15. If upgrading is not immediately possible, disable or remove the plugin if not required, and restrict access to coverage report upload functionalities to trusted users only.
Fix this in Cobertura
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2139 — 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-2139 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