Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Default inheritable capabilities for linux container should be empty

CVSS 3.1 5.9 MEDIUMEUVD CVSS 3.1 5.9 CVSS 3.1 · [email protected] · Secondary 5.9 MEDIUMCVSS 3.1 · [email protected] · Primary 5.9 MEDIUMCVSS 2.0 · [email protected] · Primary 4.6 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/moby/moby 20.10.14Fixed by github.com/docker/docker 20.10.14osv · severity unknownFixed by github.com/docker/docker 20.10.14+incompatibleFixed by github.com/moby/moby 20.10.14+incompatibleKEV status unknown

cve-program · CVE-2022-24769

Published

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers 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. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a 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.

Read the publisher's advisory

euvd · EUVD-2024-1065

Published

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers 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. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a 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.

Read the publisher's advisory

nvd · CVE-2022-24769

Published

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers 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. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a 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.

Read the publisher's advisory

osv · GHSA-2mm7-x5h6-5pvq

Published

### Impact A bug was found in Moby (Docker Engine) where containers 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. ### Patches This bug has been fixed in Moby (Docker Engine) 20.10.14. Users should update to this version as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. Refer to `capabilities(7)` for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox. ### Workarounds The entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting. ### Credits The Moby project would like to thank [Andrew G. Morgan](https://github.com/AndrewGMorgan) for responsibly disclosing this issue in accordance with the [Moby security policy](https://github.com/moby/moby/blob/master/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/moby/moby/issues/new) * Email us at [[email protected]](mailto:[email protected]) if you think you’ve found a security bug

Read the publisher's advisory

osv · GO-2022-0390

Published

Moby (Docker Engine) started with non-empty inheritable Linux process capabilities in github.com/docker/docker

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2022-24769

Published

Default inheritable capabilities for linux container should be empty

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers 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. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a 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.

Source published
24 Mar 2022 00:00:00 UTC
Source modified
3 Aug 2024 04:20:49 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 5.9 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

euvd · EUVD-2024-1065

Published

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with non-empty inheritable Linu…

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers 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. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a 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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 24, 2022, 12:00:00 AM

dateUpdated: Aug 3, 2024, 4:20:49 AM

17 related source bulletins · separate from aliases

openSUSE-SU-2025:15589-1: docker-stable-24.0.9_ce-15.1 on GA media

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-41089 · CVE-2021-41092 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23651 · CVE-2024-23652

openSUSE-SU-2024:12001-1: containerd-1.5.11-1.1 on GA media

CVE-2022-24769

RHSA-2022:1363: Red Hat Security Advisory: OpenShift Container Platform 4.9.29 bug fix and security update

CVE-2022-24769

RHSA-2022:2265: Red Hat Security Advisory: OpenShift Container Platform 4.6.58 security and extras update

CVE-2022-24769

SUSE-SU-2022:1507-1: Security update for containerd, docker

CVE-2021-41190 · CVE-2021-43565 · CVE-2022-23648 · CVE-2022-24769 · CVE-2022-27191

WID-SEC-W-2022-1738: IBM InfoSphere Information Server: Mehrere Schwachstellen

CVE-2009-0217 · CVE-2009-2625 · CVE-2012-0881 · CVE-2012-2098 · CVE-2013-2172 · CVE-2013-4002 · CVE-2013-4517 · CVE-2015-4852 · CVE-2015-6420 · CVE-2015-7501 · CVE-2017-15708 · CVE-2019-13116 · CVE-2021-33813 · CVE-2021-36373 · CVE-2021-36374 · CVE-2021-40690 · CVE-2021-41089 · CVE-2021-41091 · CVE-2022-22442 · CVE-2022-23437 · CVE-2022-24769 · CVE-2022-30608 · CVE-2022-30615 · CVE-2022-31129 · CVE-2022-35642 · CVE-2022-35717 · CVE-2022-36109 · CVE-2022-40235 · CVE-2022-40747

openSUSE-SU-2024:12002-1: docker-20.10.14_ce-1.1 on GA media

CVE-2022-24769

openSUSE-SU-2024:12074-1: runc-1.1.2-1.1 on GA media

CVE-2022-24769 · CVE-2022-29162

SUSE-SU-2025:03540-1: Security update for docker-stable

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

SUSE-SU-2022:1689-1: Security update for containerd, docker

CVE-2021-43565 · CVE-2022-23648 · CVE-2022-24769 · CVE-2022-27191

RHSA-2022:1699: Red Hat Security Advisory: OpenShift Container Platform 4.7.50 security update

CVE-2022-24769

RHSA-2022:1622: Red Hat Security Advisory: OpenShift Container Platform 4.6.57 security and extras update

CVE-2022-24769

msrc_CVE-2022-24769: Default inheritable capabilities for linux container should be empty

CVE-2022-24769

RHSA-2022:1357: Red Hat Security Advisory: OpenShift Container Platform 4.10.10 security and extras update

CVE-2022-24769

RHSA-2022:1370: Red Hat Security Advisory: OpenShift Container Platform 4.8.37 security and extras update

CVE-2022-24769

WID-SEC-W-2022-1375: JFrog Artifactory: Mehrere Schwachstellen

CVE-2013-4517 · CVE-2013-7285 · CVE-2014-0107 · CVE-2014-0114 · CVE-2014-3577 · CVE-2014-3623 · CVE-2015-0227 · CVE-2015-2575 · CVE-2015-3253 · CVE-2015-4852 · CVE-2015-7940 · CVE-2016-10750 · CVE-2016-3092 · CVE-2016-3674 · CVE-2016-6501 · CVE-2016-8735 · CVE-2016-8745 · CVE-2017-1000487 · CVE-2017-15095 · CVE-2017-17485 · CVE-2017-18214 · CVE-2017-18640 · CVE-2017-7525 · CVE-2017-7657 · CVE-2017-7957 · CVE-2017-9506 · CVE-2018-1000206 · CVE-2018-9116 · CVE-2019-10219 · CVE-2019-12402 · CVE-2019-17359 · CVE-2019-17571 · CVE-2019-20104 · CVE-2020-11996 · CVE-2020-13934 · CVE-2020-13935 · CVE-2020-13949 · CVE-2020-14340 · CVE-2020-15586 · CVE-2020-1745 · CVE-2020-17521 · CVE-2020-25649 · CVE-2020-28500 · CVE-2020-29582 · CVE-2020-36518 · CVE-2020-7226 · CVE-2020-7692 · CVE-2020-8203 · CVE-2021-13936 · CVE-2021-21290 · CVE-2021-22060 · CVE-2021-22112 · CVE-2021-22119 · CVE-2021-22147 · CVE-2021-22148 · CVE-2021-22149 · CVE-2021-22573 · CVE-2021-23337 · CVE-2021-25122 · CVE-2021-26291 · CVE-2021-27568 · CVE-2021-29505 · CVE-2021-30129 · CVE-2021-33037 · CVE-2021-35550 · CVE-2021-35556 · CVE-2021-35560 · CVE-2021-35561 · CVE-2021-35564 · CVE-2021-35565 · CVE-2021-35567 · CVE-2021-35578 · CVE-2021-35586 · CVE-2021-35588 · CVE-2021-35603 · CVE-2021-36374 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-38561 · CVE-2021-3859 · CVE-2021-41090 · CVE-2021-41091 · CVE-2021-42340 · CVE-2021-42550 · CVE-2021-43797 · CVE-2022-0536 · CVE-2022-22963 · CVE-2022-23632 · CVE-2022-23648 · CVE-2022-23806 · CVE-2022-24769 · CVE-2022-24823 · CVE-2022-27191 · CVE-2022-29153 · CVE-2022-32212 · CVE-2022-32213 · CVE-2022-32214 · CVE-2022-32215 · CVE-2022-32223

SUSE-SU-2025:03545-1: Security update for docker-stable

CVE-2014-3499 · CVE-2014-5277 · CVE-2014-6407 · CVE-2014-6408 · CVE-2014-8178 · CVE-2014-8179 · CVE-2014-9356 · CVE-2014-9357 · CVE-2014-9358 · CVE-2015-3627 · CVE-2015-3629 · CVE-2015-3630 · CVE-2015-3631 · CVE-2016-3697 · CVE-2016-8867 · CVE-2016-9962 · CVE-2017-14992 · CVE-2017-16539 · CVE-2018-10892 · CVE-2018-15664 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-20699 · CVE-2019-13509 · CVE-2019-14271 · CVE-2020-12912 · CVE-2020-13401 · CVE-2020-15257 · CVE-2020-8694 · CVE-2020-8695 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-41089 · CVE-2021-41091 · CVE-2021-41092 · CVE-2021-41103 · CVE-2021-41190 · CVE-2021-43565 · CVE-2022-24769 · CVE-2022-27191 · CVE-2022-36109 · CVE-2023-28840 · CVE-2023-28841 · CVE-2023-28842 · CVE-2024-23650 · CVE-2024-23651 · CVE-2024-23652 · CVE-2024-23653 · CVE-2024-29018 · CVE-2024-41110 · CVE-2025-22868 · CVE-2025-22869

Source published
Mar 24, 2022, 12:00:00 AM (timezone not stated)
Source modified
Aug 3, 2024, 4:20:49 AM (timezone not stated)
Saved here
16 Nov 2026 01:35:36 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 5.9 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

nvd · CVE-2022-24769

Published

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with non-empty inheritable Linu…

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers 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. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a 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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-732

Original publisher date fields

published: 2022-03-24T20:15:09.493

lastModified: 2026-06-17T04:32:28.717

7 source CPE criteria · context only
  • cpe:2.3:a:mobyproject:moby:*:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:*:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
24 Mar 2022 20:15:09 UTC
Source modified
17 Jun 2026 04:32:28 UTC
Saved here
24 Oct 2026 20:17:12 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 5.9 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

CVSS 3.1 · [email protected] · Primary · 5.9 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

CVSS 2.0 · [email protected] · Primary · 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

osv · GHSA-2mm7-x5h6-5pvq

Published

Moby (Docker Engine) started with non-empty inheritable Linux process capabilities

### Impact A bug was found in Moby (Docker Engine) where containers 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. ### Patches This bug has been fixed in Moby (Docker Engine) 20.10.14. Users should update to this version as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. Refer to `capabilities(7)` for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox. ### Workarounds The entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting. ### Credits The Moby project would like to thank [Andrew G. Morgan](https://github.com/AndrewGMorgan) for responsibly disclosing this issue in accordance with the [Moby security policy](https://github.com/moby/moby/blob/master/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/moby/moby/issues/new) * Email us at [[email protected]](mailto:[email protected]) if you think you’ve found a security bug

Source published
22 Apr 2024 18:45:21 UTC
Source modified
10 Sep 2026 03:50:10 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Publisher rating · MODERATE

osv · GO-2022-0390

Published

Moby (Docker Engine) started with non-empty inheritable Linux process capabilities in github.com/docker/docker

Moby (Docker Engine) started with non-empty inheritable Linux process capabilities in github.com/docker/docker

Source published
21 Aug 2024 14:30:31 UTC
Source modified
4 Feb 2026 03:50:43 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current