Red Hat Product Errata RHSA-2021:2130 - Security Advisory
Issued:
2021-06-23
Updated:
2021-06-23

RHSA-2021:2130 - Security Advisory

Synopsis

Moderate: Windows Container Support for Red Hat OpenShift 2.0.1 security and bug fix update

Type/Severity

Security Advisory: Moderate

Topic

The components for Windows Container Support for Red Hat OpenShift 2.0.1 are now available.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Description

Windows Container Support for Red Hat OpenShift allows you to deploy Windows container workloads running on Windows Server containers.

Security Fix(es):

  • kubernetes: LoadBalancer Service type don't create a HNS policy for empty or invalid external loadbalancer IP, what could lead to MITM (CVE-2021-25736)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

  • WMCO patch pub-key-hash annotation to Linux node (BZ#1945248)
  • LoadBalancer Service type with invalid external loadbalancer IP breaks the datapath (BZ#1952917)
  • Telemetry info not completely available to identify windows nodes (BZ#1955319)
  • WMCO incorrectly shows node as ready after a failed configuration (BZ#1956412)
  • kube-proxy service terminated unexpectedly after recreated LB service (BZ#1963263)

Solution

For Windows Machine Config Operator upgrades, see the following documentation:

https://docs.openshift.com/container-platform/4.7/windows_containers/windows-node-upgrades.html

Affected Products

  • Red Hat OpenShift Container Platform 4.7 for RHEL 8 x86_64

Fixes

  • BZ - 1945248 - WMCO patch pub-key-hash annotation to Linux node
  • BZ - 1946538 - CVE-2021-25736 kubernetes: LoadBalancer Service type don't create a HNS policy for empty or invalid external loadbalancer IP, what could lead to MITM
  • BZ - 1952917 - LoadBalancer Service type with invalid external loadbalancer IP breaks the datapath
  • BZ - 1955319 - Telemetry info not completely available to identify windows nodes
  • BZ - 1956412 - WMCO incorrectly shows node as ready after a failed configuration
  • BZ - 1963263 - kube-proxy service terminated unexpectedly after recreated LB service
  • WINC-623 - Windows Container Support for Red Hat OpenShift 2.0.1 release

The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.