Credential disclosure via plaintext configuration storage
Published Feb 12, 2020 · Updated Aug 4, 2024
Credential exposure in Jenkins DigitalOcean Plugin 1.1 and earlier allows local users to read a DigitalOcean token from controller storage. The plugin serializes the token as plaintext in the global config.xml file rather than protecting the credential at rest. Access requires permission to read the Jenkins controller file system, and disclosure enables reuse of the stored DigitalOcean credential.
Summary
What happened
Credential exposure in Jenkins DigitalOcean Plugin 1.1 and earlier allows local users to read a DigitalOcean token from controller storage. The plugin serializes the token as plaintext in the global config.xml file rather than protecting the credential at rest. Access requires permission to read the Jenkins controller file system, and disclosure enables reuse of the stored DigitalOcean credential.
The record
- CVE
- CVE-2020-2126
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins DigitalOcean Plugin
- 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 <=1.1
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