{"id":"CVE-2022-31030","aliases":["GHSA-5ffw-gxpp-mxpf","GO-2022-0482"],"title":"containerd CRI plugin: Host memory exhaustion through ExecSync","summary":"containerd CRI plugin: Host memory exhaustion through ExecSync","severity":"medium","cvss":5.5,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","vendor":"containerd","product":"github.com/containerd/containerd","ecosystem":"go","affected":["github.com/containerd/containerd < 1.5.13","github.com/containerd/containerd >= 1.6.0, < 1.6.6"],"patched":["github.com/containerd/containerd 1.5.13","github.com/containerd/containerd 1.6.6"],"published":"2022-06-06","updated":"2026-09-10","sourceUpdated":"2026-09-10T03:49:49.235350096Z","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-5ffw-gxpp-mxpf","references":[{"url":"https://github.com/containerd/containerd/security/advisories/GHSA-5ffw-gxpp-mxpf"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31030"},{"url":"https://github.com/containerd/containerd/commit/c1bcabb4541930f643aa36a2b38655e131346382"},{"url":"https://github.com/containerd/containerd"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/REOZCUAPCA7NFDWYBDYX6EYXWLHABKBO"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WSIGDBHAB3I75JBJNGWEPBTJPS2FOVHD"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/REOZCUAPCA7NFDWYBDYX6EYXWLHABKBO"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WSIGDBHAB3I75JBJNGWEPBTJPS2FOVHD"},{"url":"https://security.gentoo.org/glsa/202401-31"},{"url":"https://www.debian.org/security/2022/dsa-5162"},{"url":"http://www.openwall.com/lists/oss-security/2022/06/07/1"}],"tags":["osv","go"],"epss":0.00381,"epssPercentile":0.31864,"ingestedAt":"2026-09-12T03:13:01.755Z","slug":"CVE-2022-31030","body":"## Overview\n\n### Impact\n\nA 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.\n\n### Patches\n\nThis bug has been fixed in containerd 1.6.6 and 1.5.13.  Users should update to these versions to resolve the issue.\n\n### Workarounds\n\nEnsure that only trusted images and commands are used. \n\n### References\n\n* Similar fix in cri-o's CRI implementation https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j\n\n### Credits\n\nThe containerd project would like to thank David Korczynski and Adam Korczynski of ADA Logics for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/main/SECURITY.md) during a security audit sponsored by CNCF and facilitated by OSTIF.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)\n* Email us at [security@containerd.io](mailto:security@containerd.io)\n\n## Affected packages\n\n- `github.com/containerd/containerd < 1.5.13`\n- `github.com/containerd/containerd >= 1.6.0, < 1.6.6`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/containerd/containerd 1.5.13`\n- `github.com/containerd/containerd 1.6.6`","depth":"sunlit","depthScore":30,"depthScoreParts":{"impact":30.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}