Change Container permissions to Private for provisioned Azure Volumes #47605
@jdumars: changing LGTM is restricted to assignees, and only kubernetes org members may be assigned issues.
[APPROVALNOTIFIER] This PR is APPROVED
Associated issue: 47611
The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing
1 similar comment
This fixes a security issue, see the release notes here: https://groups.google.com/forum/#!topic/kubernetes-announce/WodXsASu6y0
A vulnerability has been disclosed in which default access permissions for Persistent Volumes (PVs) created by the Kubernetes Azure cloud provider in versions 1.6.0 to 1.6.5 are set to "container" which exposes a URI that can be accessed without authentication on the public internet. Access to the URI string requires privileged access to the Kubernetes cluster or authenticated access to the Azure portal.
The vulnerability is tracked in http://issue.k8s.io/47611, and fixed in release v1.6.6, available immediately. The fix is also included in the upcoming 1.7.0 release.
Who is affected?
Only Kubernetes 1.6.0-1.6.5 installations that have Persistent Volumes (PVs) actively provisioned through the Azure cloud provider are subject to the vulnerability. Clusters without PVs are unaffected. No other form of cluster storage is impacted.
What is the impact?
An individual with the full URI of an actively provisioned persistent volume can download the VHD file for that volume. It does not apply retroactively to volumes already deleted from the cluster.
How can I mitigate this prior to installing 1.6.6?
Permissions on running persistent volumes can be changed without affecting cluster operations using the Azure CLI or through the Azure web portal. A full procedure for both methods is available here: https://aka.ms/f5tslk
Azure Container Service rollout of 1.6.6 will begin immediately.