Cluster takeover via exposed service-account token
Published Mar 21, 2025 · Updated Mar 24, 2025
Incorrect permissions in PipeCD 0.49.3 and earlier let attackers on a Kubernetes worker node steal its service-account token. A broadly privileged PipeCD pod can be forced onto the compromised node, where its mounted token is readable and accepted by the Kubernetes API. Control of a worker node is required; the token permits access to cluster secrets and can support takeover of the Kubernetes cluster.
Summary
What happened
Incorrect permissions in PipeCD 0.49.3 and earlier let attackers on a Kubernetes worker node steal its service-account token. A broadly privileged PipeCD pod can be forced onto the compromised node, where its mounted token is readable and accepted by the Kubernetes API. Control of a worker node is required; the token permits access to cluster secrets and can support takeover of the Kubernetes cluster.
The record
- CVE
- CVE-2024-53351
- Published
- Mar 21, 2025
- Updated
- Mar 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1552.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Worker-node service-account token theft procedureproof 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