Credential exposure via escaped-dollar masking mismatch
Published May 6, 2020 · Updated Aug 4, 2024
Credential exposure in Jenkins Credentials Binding Plugin 1.22 and earlier allows remote authenticated users to read secrets from build logs. Before value expansion, the masking filter matches only the original secret and omits the dollar-escaped form containing doubled dollar signs. Exploitation requires a bound secret containing a dollar sign and a build step that prints the escaped value, exposing that credential to users who can read the log.
Summary
What happened
Credential exposure in Jenkins Credentials Binding Plugin 1.22 and earlier allows remote authenticated users to read secrets from build logs. Before value expansion, the masking filter matches only the original secret and omits the dollar-escaped form containing doubled dollar signs. Exploitation requires a bound secret containing a dollar sign and a build step that prints the escaped value, exposing that credential to users who can read the log.
The record
- CVE
- CVE-2020-2182
- Published
- May 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Credentials Binding Plugin
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 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.22
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