From 48e2935f96383c379e78dd411be67a94396ec906 Mon Sep 17 00:00:00 2001 From: CVE Team Date: Thu, 8 Nov 2018 08:54:00 -0500 Subject: [PATCH] - Updated fix information. --- 2018/2xxx/CVE-2018-2475.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2018/2xxx/CVE-2018-2475.json b/2018/2xxx/CVE-2018-2475.json index 18ab485153e..a4339ec3bdf 100644 --- a/2018/2xxx/CVE-2018-2475.json +++ b/2018/2xxx/CVE-2018-2475.json @@ -16,7 +16,7 @@ "version_data" : [ { "version_affected" : "<", - "version_value" : "0.12.2" + "version_value" : "0.12.4" } ] } @@ -35,7 +35,7 @@ "description_data" : [ { "lang" : "eng", - "value" : "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.2." + "value" : "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." } ] },