containerd CRI plugin: Host memory exhaustion through ExecSync
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| containerd | containerd | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-5162-1 | containerd security update |
EUVD |
EUVD-2022-5937 | 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. |
Github GHSA |
GHSA-5ffw-gxpp-mxpf | containerd CRI plugin: Host memory exhaustion through ExecSync |
Ubuntu USN |
USN-5521-1 | containerd vulnerabilities |
Ubuntu USN |
USN-5776-1 | containerd vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.387% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.