Rancher Project Members Have Continued Access to Namespaces After Being Removed From Them
In Rancher 2.0.0 through 2.1.5, project members have continued access to create, update, read, and delete namespaces in a project after they have been removed from it.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-6287US | high8.1 | — | ||
In Rancher 2.0.0 through 2.1.5, project members have continued access to create, update, read, and delete namespaces in a project after they have been removed from it. | ||||
02
references
External citations — patches, advisories, analysis.
- https://forums.rancher.com/t/rancher-release-v2-1-6/13148WEB
- https://forums.rancher.com/t/rancher-security-announcement-cve-2018-20321-and-cve-2019-6287/13149WEB
- https://github.com/rancher/rancherPACKAGE
- https://github.com/rancher/rancher/issues/17244WEB
- https://github.com/rancher/rancher/issues/17724WEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-6287ADVISORY
- 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