CVE-2018-20321

moderate-risk
Published 2019-04-10

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.

Do I need to act?

-
0.44% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
8
CVSS 8.8/10 High
NETWORK / LOW complexity

Affected Products (1)

Affected Vendors

Suse

References (4)

Vendor Advisory https://forums.rancher.com/c/announcements
Mitigation https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-add...
Vendor Advisory https://forums.rancher.com/c/announcements
Mitigation https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-add...
37
/ 100
moderate-risk
Severity 30/34 · Critical
Exploitability 2/34 · Minimal
Exposure 5/34 · Minimal