Access Control Bypass
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-20321US | high8.8OT elevated | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://forums.rancher.com/c/announcementsWEB
- https://github.com/rancher/rancherPACKAGE
- https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448WEB
- https://github.com/rancher/rancher/releases/tag/v2.1.6WEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-20321ADVISORY
- https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan