Secret disclosure via wildcard ClusterRole permissions
Published May 1, 2024 · Updated Aug 2, 2024
Improper access control in spidernet-io Spiderpool 0.9.3 and earlier allows local users to read Kubernetes secrets with a stolen token. The affected ClusterRole grants every verb on every Kubernetes resource, so its service-account token authorizes unrestricted API operations. Exploitation requires control of a worker node and the ability to force a Spiderpool pod onto it to obtain the token; exposed secrets can enable cluster takeover.
Summary
What happened
Improper access control in spidernet-io Spiderpool 0.9.3 and earlier allows local users to read Kubernetes secrets with a stolen token. The affected ClusterRole grants every verb on every Kubernetes resource, so its service-account token authorizes unrestricted API operations. Exploitation requires control of a worker node and the ability to force a Spiderpool pod onto it to obtain the token; exposed secrets can enable cluster takeover.
The record
- CVE
- CVE-2024-33393
- Published
- May 1, 2024
- Updated
- Aug 2, 2024
- Vendor
- spidernet-io
- Product
- Spiderpool
- Classifications
- CWE-269, CWE-284, T1078
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=- <=0.9.3
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
- Spiderpool ClusterRole abuse proof of conceptproof of concept · unverified
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