Credential disclosure via plaintext job configuration storage
Published Apr 16, 2020 · Updated Aug 4, 2024
Cleartext storage in Jenkins Project Copr Plugin 0.3 and earlier allows remote authenticated users to read Copr API credentials. In CoprPlugin.java, apilogin and apitoken were ordinary String fields, so Jenkins serialization wrote their plaintext values into each affected job's config.xml. Reading those secrets requires Extended Read permission or controller file-system access and exposes the Copr API credentials without altering jobs or service availability.
Summary
What happened
Cleartext storage in Jenkins Project Copr Plugin 0.3 and earlier allows remote authenticated users to read Copr API credentials. In CoprPlugin.java, apilogin and apitoken were ordinary String fields, so Jenkins serialization wrote their plaintext values into each affected job's config.xml. Reading those secrets requires Extended Read permission or controller file-system access and exposes the Copr API credentials without altering jobs or service availability.
The record
- CVE
- CVE-2020-2177
- Published
- Apr 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Copr Plugin
- Classifications
- CWE-256, CWE-312
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 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 <=0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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