Vulnerabilities · 2019 · Suse
CVE-2019-6287
Suse Rancher vulnerability
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.
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
- forums.rancher.com/c/announcements · Vendor Advisory
- rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher- · Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-6287
- github.com/rancher/rancher/issues/17244
- github.com/rancher/rancher/issues/17724
- forums.rancher.com/t/rancher-release-v2-1-6/13148
- forums.rancher.com/t/rancher-security-announcement-cve-2018-20321-and-cve-2019-6287/13149
- rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-
- nvd.nist.gov/vuln/detail/CVE-2019-6287
- cve.org/CVERecord?id=CVE-2019-6287
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.