RHSA-2020:1937: Moderate: OpenShift Container Platform 4.4.3 cri-o security update
Red Hat OpenShift Container Platform is Red Hat's cloud computingKubernetes application platform solution designed for on-premise or privatecloud deployments.Security Fix(es): proglottis/gpgme: Use-after-free in GPGME bindings during container image pull (CVE-2020-8945) containers/image: Container images read entire image manifest into memory (CVE-2020-1702) 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/cri-oto a version that resolves this vulnerability.Fixed in 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el8 - Upgrade
Upgrade
redhat/cri-o-debuginfoto a version that resolves this vulnerability.Fixed in 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el8 - Upgrade
Upgrade
redhat/cri-o-debugsourceto a version that resolves this vulnerability.Fixed in 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el8 - Upgrade
Upgrade
redhat/cri-oto a version that resolves this vulnerability.Fixed in 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el7 - Upgrade
Upgrade
redhat/cri-o-debuginfoto a version that resolves this vulnerability.Fixed in 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el7 - Upgrade
Upgrade
Red Hat OpenShift Container Platformto a version that resolves this vulnerability.Fixed in 4.4.3
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:1937?
The severity of RHSA-2020:1937 is classified as moderate.
How do I fix RHSA-2020:1937?
To fix RHSA-2020:1937, upgrade the CRI-O package to version 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el8 or above.
What vulnerabilities are addressed in RHSA-2020:1937?
RHSA-2020:1937 addresses a use-after-free vulnerability in GPGME bindings during container image pull.
Which versions of CRI-O are affected by RHSA-2020:1937?
Versions of CRI-O prior to 1.17.4-8.dev.rhaos4.4.git5f5c5e4.el8 are affected by RHSA-2020:1937.
Is there a workaround for RHSA-2020:1937?
There is no documented workaround for the vulnerability addressed in RHSA-2020:1937.