{"id":"CVE-2018-20321","aliases":["EUVD-2021-1305","GHSA-9qq2-xhmc-h9qr","GO-2022-0644"],"status":"published","title":"Access Control Bypass","description":"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.","severity":{"version":"3.0","score":8.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.01766,"percentile":0.78235,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-288","CWE-668"],"published":"2019-04-10T13:59:44Z","modified":"2026-10-24T10:30:35Z","fixes":[{"ecosystem":"Go","package":"github.com/rancher/rancher","fixed_in":["2.1.6","2.1.6+incompatible"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/rancher/rancher","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.1.6"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/rancher/rancher","ranges":[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.1.6"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/rancher/rancher","ranges":[{"type":"SEMVER","events":[{"introduced":"2.0.0+incompatible"},{"fixed":"2.1.6+incompatible"}]}]}],"products":[{"vendor":"suse","product":"rancher"}],"references":[{"url":"https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/","tags":["x_refsource_CONFIRM","x_transferred","Mitigation","Vendor Advisory","advisory"]},{"url":"https://forums.rancher.com/c/announcements","tags":["x_refsource_CONFIRM","x_transferred","Vendor Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-20321","tags":["advisory"]},{"url":"https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448","tags":["web","fix"]},{"url":"https://github.com/rancher/rancher/releases/tag/v2.1.6","tags":["web"]},{"url":"https://github.com/advisories/GHSA-9qq2-xhmc-h9qr","tags":["advisory"]},{"url":"https://github.com/rancher/rancher","tags":["package"]},{"url":"https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2018-20321","description":"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.","status":"published","published":"2019-04-10T13:59:44Z","modified":"2024-08-05T11:58:18.909Z","updated_at":"2026-11-02T14:34:59.872731Z"}],"euvd":[{"id":"EUVD-2021-1305","description":"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.","status":"published","published":"2019-04-10T13:59:44Z","modified":"2024-08-05T11:58:18Z","updated_at":"2026-11-03T02:39:31.423203Z"}],"ghsa":[{"id":"GHSA-9qq2-xhmc-h9qr","title":"Access Control Bypass","description":"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.","status":"published","published":"2021-06-23T17:57:10Z","modified":"2023-02-01T05:05:36Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-288","CWE-668"],"updated_at":"2026-11-02T14:36:34.917834Z"}],"nvd":[{"id":"CVE-2018-20321","description":"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.","status":"published","published":"2019-04-10T14:29:00.267Z","modified":"2026-06-17T01:52:37.003Z","cvss":[{"version":"3.0","score":8.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":9,"vector":"AV:N/AC:L/Au:S/C:C/I:C/A:C","level":"high","assessor":"primary"}],"cwes":["CWE-668"],"updated_at":"2026-11-02T14:04:55.136632Z"}],"osv":[{"id":"CVE-2018-20321","description":"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.","status":"published","published":"2019-04-10T14:29:00.267Z","modified":"2026-10-24T10:30:35.909954578Z","cvss":[{"version":"3.0","score":8.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:09.145458Z"},{"id":"GHSA-9qq2-xhmc-h9qr","title":"Access Control Bypass","description":"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.","status":"published","published":"2021-06-23T17:57:10Z","modified":"2024-08-21T15:41:59.636638Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-288","CWE-668"],"updated_at":"2026-11-02T15:46:44.225359Z"},{"id":"GO-2022-0644","title":"Access Control Bypass in github.com/rancher/rancher","description":"Access Control Bypass in github.com/rancher/rancher","status":"published","published":"2024-08-21T15:21:45Z","modified":"2026-03-03T04:50:48.465228Z","updated_at":"2026-11-02T15:47:00.918515Z"}]}}