Docker credential disclosure via plaintext configuration storage
Published Aug 31, 2021 · Updated Aug 3, 2024
Plaintext credential storage in Jenkins Nomad Plugin 0.7.4 and earlier allows local users to read Docker registry passwords. The worker-template configuration writes Docker authentication passwords directly into the controller's global config.xml file without encryption. The user must already have access to the Jenkins controller file system, and the exposure is limited to confidentiality of configured Docker credentials.
Summary
What happened
Plaintext credential storage in Jenkins Nomad Plugin 0.7.4 and earlier allows local users to read Docker registry passwords. The worker-template configuration writes Docker authentication passwords directly into the controller's global config.xml file without encryption. The user must already have access to the Jenkins controller file system, and the exposure is limited to confidentiality of configured Docker credentials.
The record
- CVE
- CVE-2021-21681
- Published
- Aug 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Nomad Plugin
- Classifications
- CWE-256, CWE-522, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.7.4
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