Resource exhaustion in Containerd
CVE-2022-31030
containerd is an open source container runtime. A bug was found in the 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. This bug has been fixed in containerd 1.6.6 and 1.5.13. Users should update to these versions to resolve the issue. Users unable to upgrade should ensure that only trusted images and commands are used.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.004, 33.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Containerd — versions < 1.5.13, >= 1.6.0, < 1.6.6
- Linuxfoundation Containerd
- Debian Linux — versions 11.0
- Fedoraproject Fedora — versions 35, 36
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (8-cm/kube-dump). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/containerd/containerd/security/advisories/GHSA-5ffw-gxpp-mxpf (Third Party Advisory)
- github.com/containerd/containerd/commit/c1bcabb4541930f643aa36a2b38655e131346382 (Product, Third Party Advisory)
- [oss-security] 20220606 CVE-2022-31030: containerd CRI plugin: Host memory exhaustion through ExecSync (mailing-list, Mailing List, Third Party Advisory)
- DSA-5162 (vendor-advisory, Third Party Advisory)
- FEDORA-2022-725ac93b48 (vendor-advisory)
- FEDORA-2022-1da581ac6d (vendor-advisory)
- GLSA-202401-31 (vendor-advisory)