Red Hat 9037 Published by

A Red Hat OpenShift Container Platform for Windows Containers 3.0.0 security and bug fix update has been released for Windows Containers 3.0.0.



RHSA-2021:3001-01: Moderate: Red Hat OpenShift Container Platform for Windows Containers 3.0.0 security and bug fix update



=====================================================================
Red Hat Security Advisory

Synopsis: Moderate: Red Hat OpenShift Container Platform for Windows Containers 3.0.0 security and bug fix update
Advisory ID: RHSA-2021:3001-01
Product: Red Hat OpenShift Enterprise
Advisory URL:   https://access.redhat.com/errata/RHSA-2021:3001
Issue date: 2021-08-03
CVE Names: CVE-2021-20206
=====================================================================

1. Summary:

The components for Red Hat OpenShift Container Platform for Windows
Containers 3.0.0 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.

2. Description:

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

Security Fix(es):

* containernetworking-cni: Arbitrary path injection via type field in CNI
configuration (CVE-2021-20206)

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):

* LB service unstable with multiple Windows nodes and pods (BZ#1905950)

* WMCO patch pub-key-hash annotation to Linux node (BZ#1930791)

* kube-proxy service terminated unexpectedly after recreated LB service
(BZ#1939968)

* Telemetry info not completely available to identify windows nodes
(BZ#1948037)

* LoadBalancer Service type with invalid external loadbalancer IP breaks
the datapath (BZ#1952914)

* WMCO incorrectly shows node as ready after a failed configuration
(BZ#1953692)

* Windows pod with a Projected Volume is stuck at ContainerCreating
(BZ#1971745)

3. Solution:

For Windows Machine Config Operator upgrades, see the following
documentation:
  https://docs.openshift.com/container-platform/latest/windows_containers/win
dows-node-upgrades.html

4. Bugs fixed (  https://bugzilla.redhat.com/):

1905950 - LB service unstable with multiple Windows nodes and pods
1919391 - CVE-2021-20206 containernetworking-cni: Arbitrary path injection via type field in CNI configuration
1930791 - WMCO patch pub-key-hash annotation to Linux node
1939968 - kube-proxy service terminated unexpectedly after recreated LB service
1948037 - Telemetry info not completely available to identify windows nodes
1952914 - LoadBalancer Service type with invalid external loadbalancer IP breaks the datapath
1953692 - WMCO incorrectly shows node as ready after a failed configuration
1971745 - Windows pod with a Projected Volume is stuck at ContainerCreating
1983153 - WMCO auto upgrade from v2.0.2 to v3.0.0 failed

5. JIRA issues fixed (  https://issues.jboss.org/):

WINC-618 - Windows Container Support for Red Hat OpenShift 3.0.0 release

6. References:

  https://access.redhat.com/security/cve/CVE-2021-20206
  https://access.redhat.com/security/updates/classification/#moderate

7. Contact:

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

Copyright 2021 Red Hat, Inc.