First published: Wed Jun 08 2022(Updated: )
Red Hat Advanced Cluster Management for Kubernetes 2.5.0 images<br>Red Hat Advanced Cluster Management for Kubernetes provides the capabilities to address common challenges that administrators and site reliability engineers face as they work across a range of public and private cloud environments. Clusters and applications are all visible and managed from a single console—with security policy built in.<br>This advisory contains the container images for Red Hat Advanced Cluster Management for Kubernetes, which fix several bugs and security issues. See the following Release Notes documentation, which will be updated shortly for this release, for additional details about this release:<br><a href="https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/release_notes/" target="_blank">https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/release_notes/</a> Security fixes: <br><li> nodejs-json-schema: Prototype pollution vulnerability (CVE-2021-3918)</li> <li> containerd: Unprivileged pod may bind mount any privileged regular file on disk (CVE-2021-43816)</li> <li> minio: user privilege escalation in AddUser() admin API (CVE-2021-43858)</li> <li> openssl: Infinite loop in BN_mod_sqrt() reachable when parsing certificates (CVE-2022-0778)</li> <li> imgcrypt: Unauthorized access to encryted container image on a shared system due to missing check in CheckAuthorization() code path (CVE-2022-24778)</li> <li> golang.org/x/crypto: empty plaintext packet causes panic (CVE-2021-43565)</li> <li> node-fetch: exposure of sensitive information to an unauthorized actor (CVE-2022-0235)</li> <li> nconf: Prototype pollution in memory store (CVE-2022-21803)</li> <li> golang: crypto/elliptic IsOnCurve returns true for invalid field elements (CVE-2022-23806)</li> <li> nats-server: misusing the "dynamically provisioned sandbox accounts" feature authenticated user can obtain the privileges of the System account (CVE-2022-24450)</li> <li> Moment.js: Path traversal in moment.locale (CVE-2022-24785)</li> <li> golang: crash in a golang.org/x/crypto/ssh server (CVE-2022-27191)</li> <li> go-getter: writes SSH credentials into logfile, exposing sensitive credentials to local uses (CVE-2022-29810)</li> <li> opencontainers: OCI manifest and index parsing confusion (CVE-2021-41190)</li> Bug fixes:<br><li> RFE Copy secret with specific secret namespace, name for source and name, namespace and cluster label for target (BZ# 2014557)</li> <li> RHACM 2.5.0 images (BZ# 2024938)</li> <li> [UI] When you delete host agent from infraenv no confirmation message appear (Are you sure you want to delete x?) (BZ#2028348)</li> <li> Clusters are in 'Degraded' status with upgrade env due to obs-controller not working properly (BZ# 2028647)</li> <li> create cluster pool -> choose infra type, As a result infra providers disappear from UI. (BZ# 2033339)</li> <li> Restore/backup shows up as Validation failed but the restore backup status in ACM shows success (BZ# 2034279)</li> <li> Observability - OCP 311 node role are not displayed completely (BZ# 2038650)</li> <li> Documented uninstall procedure leaves many leftovers (BZ# 2041921)</li> <li> infrastructure-operator pod crashes due to insufficient privileges in ACM 2.5 (BZ# 2046554)</li> <li> Acm failed to install due to some missing CRDs in operator (BZ# 2047463)</li> <li> Navigation icons no longer showing in ACM 2.5 (BZ# 2051298)</li> <li> ACM home page now includes /home/ in url (BZ# 2051299)</li> <li> proxy heading in Add Credential should be capitalized (BZ# 2051349)</li> <li> ACM 2.5 tries to create new MCE instance when install on top of existing MCE 2.0 (BZ# 2051983)</li> <li> Create Policy button does not work and user cannot use console to create policy (BZ# 2053264)</li> <li> No cluster information was displayed after a policyset was created (BZ# 2053366)</li> <li> Dynamic plugin update does not take effect in Firefox (BZ# 2053516)</li> <li> Replicated policy should not be available when creating a Policy Set (BZ# 2054431)</li> <li> Placement section in Policy Set wizard does not reset when users click "Back" to re-configured placement (BZ# 2054433)</li>
Affected Software | Affected Version | How to fix |
---|
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.