ALAS2ECS-2022-001

References: CVE-2022-23648  CVE-2022-24769  CVE-2022-31030 
FAQs regarding Amazon Linux ALAS/CVE Severity

Issue Overview:

A bug was found in containerd where containers launched through containerd's CRI implementation with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd's CRI implementation. (CVE-2022-23648)

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. (CVE-2022-24769)

A bug was found in containerd's CRI implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the ExecSync API. This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads. Kubernetes and crictl can both be configured to use containerd's CRI implementation; ExecSync may be used when running probes or when executing processes via an exec facility. (CVE-2022-31030)

Issue Correction:
Run yum update ecs-init to update your system.
Run yum update docker to update your system.
Run yum update containerd to update your system.
Run yum update runc to update your system.

New Packages:

aarch64:
    docker-20.10.13-2.amzn2.aarch64
    docker-debuginfo-20.10.13-2.amzn2.aarch64
    ecs-init-1.61.1-1.amzn2.aarch64
    runc-1.0.3-3.amzn2.aarch64
    runc-debuginfo-1.0.3-3.amzn2.aarch64
    containerd-1.4.13-3.amzn2.aarch64
    containerd-stress-1.4.13-3.amzn2.aarch64
    containerd-debuginfo-1.4.13-3.amzn2.aarch64

src:
    docker-20.10.13-2.amzn2.src
    ecs-init-1.61.1-1.amzn2.src
    runc-1.0.3-3.amzn2.src
    containerd-1.4.13-3.amzn2.src

x86_64:
    docker-20.10.13-2.amzn2.x86_64
    docker-debuginfo-20.10.13-2.amzn2.x86_64
    ecs-init-1.61.1-1.amzn2.x86_64
    runc-1.0.3-3.amzn2.x86_64
    runc-debuginfo-1.0.3-3.amzn2.x86_64
    containerd-1.4.13-3.amzn2.x86_64
    containerd-stress-1.4.13-3.amzn2.x86_64
    containerd-debuginfo-1.4.13-3.amzn2.x86_64

Changelog:

2025-04-09: CVE-2022-31030 was added to this advisory.

2023-10-06: CVE-2022-24769 was added to this advisory.