RHSA-2020:1234: Moderate: docker security and bug fix update
Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that runs virtually anywhere. Security Fix(es): runc: AppArmor/SELinux bypass with malicious image that specifies a volume at /proc (CVE-2019-16884) 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.Bug Fix(es): Whitelist statx(2) in docker (BZ#1784228) Upgrading docker resulting into increase Systemd logs (BZ#1791870) docker should be linked against gpgme-pthread (BZ#1792243) docker cannot be updated to 108 on rhos13 as a container fails to start with "pivotroot invalid argument" error. (BZ#1795376) OVS pods are unable to stop when running under docker version 1.13.1-108 (BZ#1796451)
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2020:1234?
The severity of RHSA-2020:1234 is classified as critical due to the potential for AppArmor/SELinux bypass.
How do I fix RHSA-2020:1234?
To fix RHSA-2020:1234, update the affected packages to version 1.13.1-161.git64e9980.el7_8 or later.
Which products are affected by RHSA-2020:1234?
RHSA-2020:1234 affects several Docker packages including docker, docker-client, docker-common, and others.
What type of vulnerability is present in RHSA-2020:1234?
RHSA-2020:1234 describes a vulnerability that allows a malicious image to bypass AppArmor or SELinux security settings.
Is there a known exploit for RHSA-2020:1234?
As of now, specific exploits for RHSA-2020:1234 are not publicly disclosed, but the critical nature of the vulnerability suggests potential exploitation.