Incorrect Permission Assignment for Critical Resource Affecting github.com/moby/moby/daemon package, versions <20.10.14
Snyk CVSS
Threat Intelligence
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-GOLANG-GITHUBCOMMOBYMOBYDAEMON-2433098
- published 25 Mar 2022
- disclosed 25 Mar 2022
- credit Andrew G. Morgan
Introduced: 25 Mar 2022
CVE-2022-24769 Open this link in a new tabHow to fix?
Upgrade github.com/moby/moby/daemon to version 20.10.14 or higher.
Overview
Affected versions of this package are vulnerable to Incorrect Permission Assignment for Critical Resource via containers that were incorrectly started 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). Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted. 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. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset.
Workaround
The entry point of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.