From URL: RunC allowed additional container processes via `runc exec` to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container Applied a patch that should fix the vulnerability in 1.0.0_rc2-r2.
@ Arches, please test and mark stable: =app-emulation/runc-1.0.0_rc2-r2
Please re-CC amd64 when the dependent test failure is resolved.
(In reply to Aaron Bauman from comment #2) > Please re-CC amd64 when the dependent test failure is resolved. test failures do not block security bugs. Please proceed
(In reply to Agostino Sarubbo from comment #3) > (In reply to Aaron Bauman from comment #2) > > Please re-CC amd64 when the dependent test failure is resolved. > > test failures do not block security bugs. Please proceed My fault. amd64 stable.
@maintainers, please clean the vulnerable versions.
This issue was resolved and addressed in GLSA 201701-34 at https://security.gentoo.org/glsa/201701-34 by GLSA coordinator Aaron Bauman (b-man).
reopened for cleanup.
Cleaned up: commit b957c6bcb4ec8cd6fca134a865fc77ea2c05fe9e Author: Manuel Rüger <mrueg@gentoo.org> Date: Mon Feb 6 15:30:53 2017 +0100 app-emulation/runc: Remove old Package-Manager: Portage-2.3.3, Repoman-2.3.1
Repository is now clean, all done.