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.
Platform | Package | Release Date | Advisory |
---|---|---|---|
Amazon Linux 1 | containerd | 2022-06-06 19:52 | ALAS-2022-1600 |
Amazon Linux 2 - Docker Extra | containerd | 2022-06-06 19:54 | ALAS2DOCKER-2022-019 |
Amazon Linux 2 - Aws-nitro-enclaves-cli Extra | containerd | 2022-06-06 20:01 | ALAS2NITRO-ENCLAVES-2022-020 |
Amazon Linux 2023 | containerd | 2023-02-17 20:46 | ALAS2023-2023-079 |
Score Type | Score | Vector | |
---|---|---|---|
Amazon Linux | CVSSv3 | 4.4 | AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
NVD | CVSSv3 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
NVD | CVSSv2 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |