Credential ID enumeration via missing permission checks
Published Jun 10, 2021 · Updated Aug 3, 2024
Missing authorization in Jenkins Kubernetes CLI Plugin 1.10.0 and earlier allows remote authenticated users to enumerate credential IDs. Several plugin HTTP endpoints omit permission checks before returning credential identifiers. Overall/Read permission is required, and the exposure discloses identifiers that can support later credential-capture attacks but does not itself alter data.
Summary
What happened
Missing authorization in Jenkins Kubernetes CLI Plugin 1.10.0 and earlier allows remote authenticated users to enumerate credential IDs. Several plugin HTTP endpoints omit permission checks before returning credential identifiers. Overall/Read permission is required, and the exposure discloses identifiers that can support later credential-capture attacks but does not itself alter data.
The record
- CVE
- CVE-2021-21661
- Published
- Jun 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Kubernetes CLI
- Classifications
- CWE-862, T1087
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 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 <=1.10.0
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.
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