Cluster takeover via unlabeled tenant namespaces
Published Jun 29, 2023 · Updated Nov 6, 2024
Improper authentication in Sealos before 4.2.1-rc4 allows remote authenticated users to gain control of the deployed Kubernetes cluster. Affected builds do not reconcile Pod Security labels onto tenant namespaces whose names begin with ns-, leaving the intended isolation unenforced. A low-privileged Sealos public-cloud account is sufficient to control pods and other resources across the cluster.
Summary
What happened
Improper authentication in Sealos before 4.2.1-rc4 allows remote authenticated users to gain control of the deployed Kubernetes cluster. Affected builds do not reconcile Pod Security labels onto tenant namespaces whose names begin with ns-, leaving the intended isolation unenforced. A low-privileged Sealos public-cloud account is sufficient to control pods and other resources across the cluster.
The record
- CVE
- CVE-2023-33190
- Published
- Jun 29, 2023
- Updated
- Nov 6, 2024
- Vendor
- Labring
- Product
- Sealos
- Classifications
- CWE-287, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 29, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 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 <4.2.1-rc4
- Affected versionversion=< 4.2.1-rc4
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