The docker packages version docker-1.13.1-108.git4ef4b30.el7 as released for Red Hat Enterprise Linux 7 Extras via RHBA-2020:0053 (https://access.redhat.com/errata/RHBA-2020:0053) included an incorrect version of runc that was missing multiple bug and security fixes. One of the fixes regressed in that update was the fix for CVE-2019-5736, that was previously corrected in the docker packages in Red Hat Enterprise Linux 7 Extras via RHSA-2019:0304 (https://access.redhat.com/errata/RHSA-2019:0304). The CVE-2020-14298 was assigned to this security regression and it is specific to the docker packages produced by Red Hat.
The original issue - CVE-2019-5736 - could possibly allow a privileged process inside container to compromise a process entering container namespace and execute arbitrary code outside of the container. This could lead to compromise of the container host or other containers running on the same container host. For more details about the original issue, see:
This regression as corrected in docker-1.13.1-109.gitcccb291.el7_7 released via RHBA-2020:0427 (https://access.redhat.com/errata/RHBA-2020:0427).
This issue is mitigated on Red Hat Enterprise Linux 7 if SELinux is in enforcing mode, which prevents containers from escaping to the host machine.
This issue only affects a single version of docker, 1.13.1-108.git4ef4b30.el7, shipped in Red Hat Enterprise Linux 7 Extras. Both earlier and later versions are not affected.
This issue is not exploitable on Red Hat Enterprise Linux Atomic Host 7 as the exploit requires replacement of the docker-runc binary, which is stored on a read-only filesystem and cannot be overwritten.
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7 Extras
Via RHSA-2020:2653 https://access.redhat.com/errata/RHSA-2020:2653
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):