Credential ID disclosure via unchecked form enumeration
Published Feb 12, 2020 · Updated Aug 4, 2024
Information disclosure in Jenkins Pipeline GitHub Notify Step 1.0.4 and earlier allows remote authenticated users to enumerate credential IDs. The doFillCredentialsIdItems form method returns applicable credential IDs without first enforcing Item/Configure permission. Overall/Read access is sufficient; the exposed IDs do not reveal secret values directly but can support a separate credential-capture flaw.
Summary
What happened
Information disclosure in Jenkins Pipeline GitHub Notify Step 1.0.4 and earlier allows remote authenticated users to enumerate credential IDs. The doFillCredentialsIdItems form method returns applicable credential IDs without first enforcing Item/Configure permission. Overall/Read access is sufficient; the exposed IDs do not reveal secret values directly but can support a separate credential-capture flaw.
The record
- CVE
- CVE-2020-2118
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline GitHub Notify Step
- Classifications
- CWE-276
- 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.0.4
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