- Updated fix information.

This commit is contained in:
CVE Team 2018-11-08 08:54:00 -05:00
parent f04e8b798e
commit 48e2935f96
No known key found for this signature in database
GPG Key ID: 0DA1F9F56BC892E8

View File

@ -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."
}
]
},