CWE
22
Advisory Published

RHSA-2022:1681: Moderate: Red Hat Advanced Cluster Management 2.4.4 security updates and bug fixes

First published: Tue May 03 2022(Updated: )

Red Hat Advanced Cluster Management for Kubernetes 2.4.4 images<br>Red Hat Advanced Cluster Management for Kubernetes provides the<br>capabilities to address common challenges that administrators and site<br>reliability engineers face as they work across a range of public and<br>private cloud environments. Clusters and applications are all visible and<br>managed from a single console—with security policy built in.<br>This advisory contains the container images for Red Hat Advanced Cluster<br>Management for Kubernetes, which fix several bugs. See the following<br>Release Notes documentation, which will be updated shortly for this<br>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.4/html/release_notes/" target="_blank">https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.4/html/release_notes/</a> Security fixes:<br><li> Vm2: vulnerable to Sandbox Bypass (CVE-2021-23555)</li> <li> Golang.org/x/crypto: empty plaintext packet causes panic (CVE-2021-43565)</li> <li> Follow-redirects: Exposure of Private Personal Information to an Unauthorized Actor (CVE-2022-0155)</li> <li> Node-fetch: exposure of sensitive information to an unauthorized actor (CVE-2022-0235)</li> <li> Follow-redirects: Exposure of Sensitive Information via Authorization Header leak (CVE-2022-0536)</li> <li> Urijs: Authorization Bypass Through User-Controlled Key (CVE-2022-0613)</li> <li> Nconf: Prototype pollution in memory store (CVE-2022-21803)</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> Urijs: Leading white space bypasses protocol validation (CVE-2022-24723)</li> <li> Node-forge: Signature verification leniency in checking `digestAlgorithm` structure can lead to signature forgery (CVE-2022-24771)</li> <li> Node-forge: Signature verification failing to check tailing garbage bytes can lead to signature forgery (CVE-2022-24772)</li> <li> Node-forge: Signature verification leniency in checking `DigestInfo` structure (CVE-2022-24773)</li> <li> Cross-fetch: Exposure of Private Personal Information to an Unauthorized Actor (CVE-2022-1365)</li> <li> Moment.js: Path traversal in moment.locale (CVE-2022-24785)</li> Bug fixes:<br><li> Failed ClusterDeployment validation errors do not surface through the ClusterPool UI (Bugzilla #1995380)</li> <li> Agents wrong validation failure on failing to fetch image needed for installation (Bugzilla #2008583)</li> <li> Fix catalogsource name (Bugzilla #2038250)</li> <li> When the ocp console operator is disable on the managed cluster, the cluster claims failed to update (Bugzilla #2057761)</li> <li> Multicluster-operators-hub-subscription OOMKilled (Bugzilla #2053308)</li> <li> RHACM 2.4.1 Console becomes unstable and refuses login after one hour (Bugzilla #2061958)</li> <li> RHACM 2.4.4 images (Bugzilla #2077548)</li>

Affected SoftwareAffected VersionHow to fix
Red Hat Advanced Cluster Management

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of RHSA-2022:1681?

    The severity of RHSA-2022:1681 is classified as critical due to the impact on system security and application performance.

  • What software is affected by RHSA-2022:1681?

    RHSA-2022:1681 affects Red Hat Advanced Cluster Management for Kubernetes version 2.4.4.

  • How do I fix RHSA-2022:1681?

    To fix RHSA-2022:1681, you should update to the recommended version of Red Hat Advanced Cluster Management for Kubernetes as specified in the advisory.

  • What are the risks of not addressing RHSA-2022:1681?

    Not addressing RHSA-2022:1681 can lead to vulnerabilities that may be exploited, resulting in potential data breaches and loss of control over deployments.

  • Can I temporarily mitigate the effects of RHSA-2022:1681?

    Temporary mitigation measures may include applying security best practices and limiting access until a patch is applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203