Arbitrary file overwrite via unsanitized XML paths
Published Mar 9, 2020 · Updated Aug 4, 2024
An arbitrary file write in Jenkins Cobertura Plugin 1.15 and earlier allows remote authenticated users to overwrite files via crafted coverage XML. The plugin parses file paths from the coverage report XML without validating that they remain under the configured base directory. Exploitation requires permission to control the Publish Cobertura Coverage Report input, and the consequence is integrity loss on the Jenkins controller filesystem.
Summary
What happened
An arbitrary file write in Jenkins Cobertura Plugin 1.15 and earlier allows remote authenticated users to overwrite files via crafted coverage XML. The plugin parses file paths from the coverage report XML without validating that they remain under the configured base directory. Exploitation requires permission to control the Publish Cobertura Coverage Report input, and the consequence is integrity loss on the Jenkins controller filesystem.
The record
- CVE
- CVE-2020-2139
- Published
- Mar 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Cobertura Plugin
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=1.15
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo