Linux Security
    Linux Security
    Linux Security

    RedHat: RHSA-2020-5614:01 Important: OpenShift Container Platform 4.6.9

    Date 21 Dec 2020
    Posted By LinuxSecurity Advisories
    Red Hat OpenShift Container Platform release 4.6.9 is now available with updates to packages and images that fix several bugs and add enhancements. This release also includes a security update for Red Hat OpenShift Container Platform 4.6.
    Hash: SHA256
                       Red Hat Security Advisory
    Synopsis:          Important: OpenShift Container Platform 4.6.9 security and bug fix update
    Advisory ID:       RHSA-2020:5614-01
    Product:           Red Hat OpenShift Enterprise
    Advisory URL:
    Issue date:        2020-12-21
    CVE Names:         CVE-2020-1971 CVE-2020-8177 CVE-2020-15862 
                       CVE-2020-16166 CVE-2020-27836 
    1. Summary:
    Red Hat OpenShift Container Platform release 4.6.9 is now available with
    updates to packages and images that fix several bugs and add enhancements.
    This release also includes a security update for Red Hat OpenShift
    Container Platform 4.6.
    Red Hat Product Security has rated this update as having a security impact
    of Important. 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:
    Red Hat OpenShift Container Platform is Red Hat's cloud computing
    Kubernetes application platform solution designed for on-premise or private
    cloud deployments.
    Security Fix(es):
    * cluster-ingress-operator: changes to loadBalancerSourceRanges overwritten
    by operator (CVE-2020-27836)
    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.
    This advisory contains the container images for Red Hat OpenShift Container
    Platform 4.6.9. See the following advisory for the RPM packages for this
    Space precludes documenting all of the container images in this advisory.
    See the following Release Notes documentation, which will be updated
    shortly for this release, for details about these changes:
    This update fixes the following bugs among others:
    * Previously, pre-flight installer validation for OpenShift Container
    Platform on OpenStack was performed on the flavor metadata. This could
    prevent installations to flavors detected as `baremetal`, which might have
    the required capacity to complete the installation. This is usually caused
    by OpenStack administrators not setting the appropriate metadata on their
    bare metal flavors. Validations are now skipped on flavors detected as
    `baremetal`, to prevent incorrect failures from being reported.
    * Previously, there was a broken link on the OperatorHub install page of
    the web console, which was intended to reference the cluster monitoring
    documentation. This has been fixed. (BZ#1904600)
    You may download the oc tool and use it to inspect release image metadata
    as follows:
    (For x86_64 architecture)
      $ oc adm release info
    The image digest is
    (For s390x architecture)
      $ oc adm release info
    The image digest is
    (For ppc64le architecture)
      $ oc adm release info
    The image digest is
    All OpenShift Container Platform 4.6 users are advised to upgrade to these
    updated packages and images when they are available in the appropriate
    release channel. To check for available updates, use the OpenShift Console
    or the CLI oc command. Instructions for upgrading a cluster are available
    - -between-minor.html#understanding-upgrade-channels_updating-cluster-between
    - -minor.
    3. Solution:
    For OpenShift Container Platform 4.6 see the following documentation, which
    will be updated shortly for this release, for important instructions on how
    to upgrade your cluster and fully apply this asynchronous errata update:
    Details on how to access this content are available at
    - -cli.html.
    4. Bugs fixed (
    1885442 - Console doesn't load in iOS Safari when using self-signed certificates
    1885946 - console-master-e2e-gcp-console test periodically fail due to no Alerts found
    1887551 - Unsupported access mode should not be available to select when creating pvc by aws-ebs-csi-driver(gp2-csi) from web-console
    1888165 - [release 4.6] IO doesn't recognize namespaces - 2 resources with the same name in 2 namespaces -> only 1 gets collected
    1888650 - Fix CVE-2015-7501 affecting agent-maven-3.5
    1888717 - Cypress:  Fix 'link-name' accesibility violation
    1888721 - ovn-masters stuck in crashloop after scale test
    1890993 - Selected Capacity is showing wrong size
    1890994 - When the user clicked cancel at the Create Storage Class confirmation dialog all the data from the Local volume set goes off
    1891427 - CLI does not save login credentials as expected when using the same username in multiple clusters
    1891454 - EgressNetworkPolicy does not work when setting Allow rule to a dnsName
    1891499 - Other machine config pools do not show during update
    1891891 - Wrong detail head on network policy detail page.
    1896149 - TLS secrets are not able to edit on console.
    1896625 - with Serverless 1.10 version of trigger/subscription/channel/IMC is V1 as latest
    1897019 - "Attach to Virtual Machine OS" button should not be visible on old clusters
    1897766 - [release-4.6]Incorrect instructions in the Serverless operator and application quick starts
    1898172 - installer missing permission definitions for TagResources and UntagResources when installing in existing VPC
    1898302 - E2E test: Use KUBEADM_PASSWORD_FILE by default
    1898746 - opm index add cannot batch add multiple bundles that use skips
    1899056 - Max unavailable and Max surge value are not shown on Deployment Config Details page
    1899382 - Remove TechPreview Badge from Eventing in Serverless version 1.11.0
    1899728 - overview filesystem utilization of OCP is showing the wrong values
    1901110 - pod donut shows incorrect information
    1901871 - catalog-operator repeatedly crashes with "runtime error: index out of range [0] with length 0"
    1901877 - linuxptp-daemon crash when enable debug log level [release-4.6]
    1902029 - [sig-builds][Feature:Builds][valueFrom] process valueFrom in build strategy environment variables  should successfully resolve valueFrom in docker build environment variables
    1904014 - (release 4.6) Hostsubnet gatherer produces wrong output
    1904028 - [release-4.6] The quota controllers should resync on new resources and make progress
    1904065 - [release 4.6] [Openstack] HTTP_PROXY setting for NetworkManager-resolv-prepender not working
    1904260 - VPA-operator has version: 1.0.0 every build
    1904583 - Operator upgrades can delete existing CSV before completion
    1904600 - Cluster monitoring documentation link is broken - 404 not found
    1905004 - Use new packages for ipa ramdisks
    1905230 - Multus errors when cachefile is not found
    1905619 - [4.6.z] usbguard extension fails to install because of missing correct protobuf dependency version
    1905622 - [Platform] Remove restriction on disk type selection for LocalVolumeSet
    1905746 - Subscription manual approval test is flaky
    1905903 - Rules in kube-apiserver.rules are taking too long and consuming too much memory for Prometheus to evaluate them
    1906267 - CVE-2020-27836 cluster-ingress-operator: changes to loadBalancerSourceRanges overwritten by operator
    1906416 - Errant change to lastupdatetime in copied CSV status can trigger runaway csv syncs
    5. References:
    6. Contact:
    The Red Hat security contact is . More contact
    details at
    Copyright 2020 Red Hat, Inc.
    Version: GnuPG v1
    -----END PGP SIGNATURE-----
    RHSA-announce mailing list
    This email address is being protected from spambots. You need JavaScript enabled to view it.


    LinuxSecurity Poll

    'Tis the season of giving! How have you given back to the open-source community?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    [{"id":"171","title":"I've contributed to the development of an open-source project.","votes":"22","type":"x","order":"1","pct":34.92,"resources":[]},{"id":"172","title":"I've reviewed open-source code for security bugs.","votes":"13","type":"x","order":"2","pct":20.63,"resources":[]},{"id":"173","title":"I've made a donation to an open-source project.","votes":"28","type":"x","order":"3","pct":44.44,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350

    Please vote first in order to view vote results.


    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.