Incorrect Default Permissions Affecting runc Open this link in a new tab package, versions <1.1.2-r0
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications-
snyk-id
SNYK-ALPINE315-RUNC-2823418
-
published
12 May 2022
-
disclosed
17 May 2022
How to fix?
Upgrade Alpine:3.15 runc to version 1.1.2-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply to the upstream runc package.
See How to fix? for Alpine:3.15 relevant versions.
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where runc exec --cap created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes runc exec --cap behavior such that the additional capabilities granted to the process being executed (as specified via --cap arguments) do not include inheritable capabilities. In addition, runc spec is changed to not set any inheritable capabilities in the created example OCI spec (config.json) file.