CVE intelligence and bounded remediation

CVE-2022-24769 — Moby is an open-source project created by Docker to enable and accelerate software containerization

Medium CVSS 5.9

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…

Severity
Medium
CVSS
5.9 (3.1)
Published
2022-03-24
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-732

Affected products

  • mobyproject / moby
  • fedoraproject / fedora / 34
  • fedoraproject / fedora / 35
  • fedoraproject / fedora / 36
  • linuxfoundation / runc
  • debian / debian_linux / 11.0

Matched remediation archetype

Privilege escalation and unsafe privilege management

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map service accounts, operating-system identities, roles, capabilities, impersonation, set-user transitions, and administrative helper paths.
  • Determine whether untrusted users or lower-privilege processes can reach the affected transition or modify inputs it trusts.
  • Review file, socket, registry, device, job, container, and cloud-role permissions used before and after privilege changes.

Remediate safely

  • Apply the supported fix and redesign privileged operations as a minimal, authenticated, allowlisted interface.
  • Drop privileges before processing untrusted input, verify the drop succeeds, and remove unnecessary roles, capabilities, and write permissions.
  • Validate ownership and permissions at time of use and add explicit lower-to-higher privilege boundary tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.