An issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher.
References
Link | Resource |
---|---|
https://forums.rancher.com/c/announcements | Vendor Advisory |
https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/ | Mitigation Vendor Advisory |
https://forums.rancher.com/c/announcements | Vendor Advisory |
https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/ | Mitigation Vendor Advisory |
Configurations
History
21 Nov 2024, 04:01
Type | Values Removed | Values Added |
---|---|---|
References | () https://forums.rancher.com/c/announcements - Vendor Advisory | |
References | () https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/ - Mitigation, Vendor Advisory |
Information
Published : 2019-04-10 14:29
Updated : 2024-11-21 04:01
NVD link : CVE-2018-20321
Mitre link : CVE-2018-20321
CVE.ORG link : CVE-2018-20321
JSON object : View
Products Affected
suse
- rancher
CWE
CWE-668
Exposure of Resource to Wrong Sphere