Bug 1173421 (CVE-2020-14298)

Summary: VUL-0: CVE-2020-14298: docker: Security regression of due to inclusion of vulnerable runc
Product: [Novell Products] SUSE Security Incidents Reporter: Marcus Meissner <meissner>
Component: IncidentsAssignee: Containers Team <containers-bugowner>
Status: RESOLVED INVALID QA Contact: Security Team bot <security-team>
Severity: Major    
Priority: P5 - None CC: asarai, smash_bz
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/262188/
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Marcus Meissner 2020-06-26 14:20:14 UTC

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

Comment 1 Marcus Meissner 2020-06-26 14:20:42 UTC
i think this is Redhat specific.
Comment 2 Aleksa Sarai 2020-06-27 08:09:35 UTC
(In reply to Marcus Meissner from comment #1)
> i think this is Redhat specific.

I believe so too. In fact we have %check scripts in our specfiles to make sure that we are shipping the same runc commit that Docker requires (and we add CVE patches when they come up) so we wouldn't have been able to easily cause something like this by accident.