Cluster compromise via writable node-join temporary file
Published Feb 11, 2021 · Updated Sep 16, 2024
Insecure temporary-file handling in SUSE CaaS Platform 4.5 allows local users to read or alter skuba node-join configuration. During a node join, skuba places configuration containing the bootstrapToken in /tmp and later processes that file without preventing other local users from reading or changing it. Exploitation requires local access while a node is joining and enables token disclosure or arbitrary machine and cluster configuration changes.
Summary
What happened
Insecure temporary-file handling in SUSE CaaS Platform 4.5 allows local users to read or alter skuba node-join configuration. During a node join, skuba places configuration containing the bootstrapToken in /tmp and later processes that file without preventing other local users from reading or changing it. Exploitation requires local access while a node is joining and enables token disclosure or arbitrary machine and cluster configuration changes.
The record
- CVE
- CVE-2020-8030
- Published
- Feb 11, 2021
- Updated
- Sep 16, 2024
- Vendor
- SUSE
- Product
- SUSE CaaS Platform
- Classifications
- CWE-377, T1552.001, T1565.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=suba <2.1.7
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