Credential disclosure via plaintext job configuration storage
Published Feb 12, 2020 · Updated Aug 4, 2024
Plaintext credential storage in Jenkins Applatix Plugin 1.1 and earlier allows remote authenticated users to read the Applatix password. The job configuration save path writes the configured password directly into each job's config.xml without encryption. Extended Read permission exposes the credential remotely, while Jenkins controller file-system access exposes it locally.
Summary
What happened
Plaintext credential storage in Jenkins Applatix Plugin 1.1 and earlier allows remote authenticated users to read the Applatix password. The job configuration save path writes the configured password directly into each job's config.xml without encryption. Extended Read permission exposes the credential remotely, while Jenkins controller file-system access exposes it locally.
The record
- CVE
- CVE-2020-2133
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Applatix
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- 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