CVE-2019-16884

runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker image can mount over a /proc directory.

Weakness

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Affected Software

Name	Vendor	Start Version	End Version
Runc	Linuxfoundation	0.0.1 (including)	0.1.1 (including)
Runc	Linuxfoundation	1.0.0-rc1 (including)	1.0.0-rc1 (including)
Runc	Linuxfoundation	1.0.0-rc2 (including)	1.0.0-rc2 (including)
Runc	Linuxfoundation	1.0.0-rc3 (including)	1.0.0-rc3 (including)
Runc	Linuxfoundation	1.0.0-rc4 (including)	1.0.0-rc4 (including)
Runc	Linuxfoundation	1.0.0-rc5 (including)	1.0.0-rc5 (including)
Runc	Linuxfoundation	1.0.0-rc6 (including)	1.0.0-rc6 (including)
Runc	Linuxfoundation	1.0.0-rc7 (including)	1.0.0-rc7 (including)
Runc	Linuxfoundation	1.0.0-rc8 (including)	1.0.0-rc8 (including)
Red Hat Enterprise Linux 7 Extras	RedHat	runc-0:1.0.0-67.rc10.el7_8	*
Red Hat Enterprise Linux 7 Extras	RedHat	docker-2:1.13.1-161.git64e9980.el7_8	*
Red Hat Enterprise Linux 8	RedHat	container-tools:rhel8-8010020191126140055.c294d161	*
Red Hat OpenShift Container Platform 4.1	RedHat	runc-0:1.0.0-62.rc8.rhaos4.1.git3cbe540.el8	*
Red Hat OpenShift Container Platform 4.2	RedHat	runc-0:1.0.0-63.rc8.el8	*
Runc	Ubuntu	bionic	*
Runc	Ubuntu	devel	*
Runc	Ubuntu	disco	*
Runc	Ubuntu	eoan	*
Runc	Ubuntu	esm-apps/bionic	*
Runc	Ubuntu	esm-apps/xenial	*
Runc	Ubuntu	esm-infra/focal	*
Runc	Ubuntu	focal	*
Runc	Ubuntu	groovy	*
Runc	Ubuntu	hirsute	*
Runc	Ubuntu	impish	*
Runc	Ubuntu	jammy	*
Runc	Ubuntu	trusty	*
Runc	Ubuntu	upstream	*
Runc	Ubuntu	xenial	*

Potential Mitigations

Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2019-16884
CWE	https://cwe.mitre.org/data/definitions/863.html

Incorrect Authorization

Weakness

Affected Software

Potential Mitigations

References