ALT-PU-2020-3396: package helm update to version 3.4.1-alt1
Описание
This update upgrades helm to version 3.4.1-alt1.
Устраненные уязвимости6
Ссылки7
GHSA-9vp5-m38w-j776
https://github.com/advisories/GHSA-9vp5-m38w-j776GHSA-c52f-pq47-2r9j
https://github.com/advisories/GHSA-c52f-pq47-2r9jGHSA-jm56-5h66-w453
https://github.com/advisories/GHSA-jm56-5h66-w453GHSA-m54r-vrmv-hw33
https://github.com/advisories/GHSA-m54r-vrmv-hw33GHSA-q8q8-93cv-v6h8
https://github.com/advisories/GHSA-q8q8-93cv-v6h8GHSA-qq3j-xp49-j73f
https://github.com/advisories/GHSA-qq3j-xp49-j73fСвязанные уязвимости
Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package
Their is an information disclosure vulnerability in Helm from version 3.1.0 and before version 3.2.0. `lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates. The documented behavior of `helm template` states that it does not attach to a remote cluster. However, a the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior. Running `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability. A malicious chart author could inject a `lookup` into a chart that, when rendered through ...
Their is an information disclosure vulnerability in Helm from version 3.1.0 and before version 3.2.0. `lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates. The documented behavior of `helm template` states that it does not attach to a remote cluster. However, a the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior. Running `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability. A malicious chart author could inject a `lookup` into a chart that, when rendered through ...
Their is an information disclosure vulnerability in Helm from version 3.1.0 and before version 3.2.0. `lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates. The documented behavior of `helm template` states that it does not attach to a remote cluster. However, a the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior. Running `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability. A malicious chart author could inject a `lookup` into a chart that, when rendered through `he
Their is an information disclosure vulnerability in Helm from version ...