SCM credential disclosure via plaintext global configuration
Published Feb 12, 2020 · Updated Aug 4, 2024
Credential exposure in Jenkins Project Harvest SCM 0.5.1 and earlier allows local users to read SCM passwords from the controller. The plugin writes the configured SCM password without encryption to hudson.plugins.harvest.HarvestSCM.xml in the controller's Jenkins home. Access to the controller file system is required, and disclosure is limited to the stored SCM credential.
Summary
What happened
Credential exposure in Jenkins Project Harvest SCM 0.5.1 and earlier allows local users to read SCM passwords from the controller. The plugin writes the configured SCM password without encryption to hudson.plugins.harvest.HarvestSCM.xml in the controller's Jenkins home. Access to the controller file system is required, and disclosure is limited to the stored SCM credential.
The record
- CVE
- CVE-2020-2130
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Harvest SCM
- Classifications
- CWE-522, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 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.5.1
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