CVE-2018-2475
Gardener vulnerability
Following the Gardener architecture, the Kubernetes apiserver of a Gardener managed shoot cluster resides in the corresponding seed cluster. Due to missing network isolation a shoot's apiserver can access services/endpoints in the private network of its corresponding seed cluster. Combined with other minor Kubernetes security issues, the missing network isolation theoretically can lead to compromise other shoot or seed clusters in the "Gardener" context. The issue is rated high due to the high impact of a potential exploitation in "Gardener" context. This was fixed in Gardener release 0.12.4.
Affected products
Gardener. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Gardener 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
- launchpad.support.sap.com/#/notes/2699726 · Vendor Advisory
- wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=500633095 · Vendor Advisory
- www.securityfocus.com/bid/105579 · Third Party Advisory
- groups.google.com/forum/#%21topic/gardener/OjfKEe1LwXo
- nvd.nist.gov/vuln/detail/CVE-2018-2475
- cve.org/CVERecord?id=CVE-2018-2475
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.