Vulnerabilities · 2018 · Suse
CVE-2018-20321
Suse Rancher vulnerability
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.
Affected products
Rancher. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Suse Rancher runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
More vulnerabilities in Suse products
CVE-2025-6018CVE-2024-46956CVE-2024-46955CVE-2024-46953CVE-2024-46951CVE-2024-23301CVE-2023-34256CVE-2023-32186All 1,008
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.