CVE-2022-31030

containerd CRI plugin: Host memory exhaustion through ExecSync

Description

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.

Category

5.5
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.08%
Vendor Advisory debian.org Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory gentoo.org
Affected: containerd containerd
Published at:
Updated at:

References

Link Tags
https://github.com/containerd/containerd/security/advisories/GHSA-5ffw-gxpp-mxpf third party advisory
https://github.com/containerd/containerd/commit/c1bcabb4541930f643aa36a2b38655e131346382 product third party advisory
http://www.openwall.com/lists/oss-security/2022/06/07/1 third party advisory mailing list
https://www.debian.org/security/2022/dsa-5162 third party advisory vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WSIGDBHAB3I75JBJNGWEPBTJPS2FOVHD/ vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/REOZCUAPCA7NFDWYBDYX6EYXWLHABKBO/ vendor advisory
https://security.gentoo.org/glsa/202401-31 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-31030?
CVE-2022-31030 has been scored as a medium severity vulnerability.
How to fix CVE-2022-31030?
To fix CVE-2022-31030, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-31030 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-31030 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-31030?
CVE-2022-31030 affects containerd containerd.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.