Gardener Security Announcement - CVE-2018-2475 published, please update to Gardener 0.12.2

[Frederik Thormaehlen]

We have recently released Gardener 0.12.2 [0] where we continued to address the same security issue related to missing network isolation in the Gardener context as we have already started in the Gardener release 0.11.0 [1]. 

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 the Gardener context.

We recommend all Gardener instances to update immediately to Gardener release 0.12.2 or higher.

Today we published as well a dedicated Gardener CVE-2018-2475 via MITRE [2] and later via NVD [3].

The following Gardener pull requests are fixing this vulnerability: PR #266 [4] , PR #336 [5], PR #381 [6]

As a reminder, if you find a security vulnerability in Gardener, please report it following the Gardener security disclosure process [7] which is appropriate for your finding.

Thanks,

Frederik Thormaehlen (on behalf of the Gardener Security Team)

[0] https://github.com/gardener/gardener/releases

[1] https://groups.google.com/forum/#!topic/gardener/-RkBPnuucEs

[2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2475

[3] https://nvd.nist.gov/vuln/detail/CVE-2018-2475

[4] https://github.com/gardener/gardener/pull/266

[5] https://github.com/gardener/gardener/pull/336

[6] https://github.com/gardener/gardener/pull/381

[7] https://github.com/gardener/documentation/blob/master/security-release-process.md#disclosures