containerd CRI server: Host memory exhaustion through Attach goroutine leak
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd Go |
|
|
| github.com/containerd/containerd/v2 Go |
|
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd Go |
|
|
| github.com/containerd/containerd/v2 Go |
|
2.0.72.1.52.2.0containerd is an open-source container runtime. Versions 1.7.28 and below, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4, and 2.2.0-beta.0 through 2.2.0-rc.1 contain a bug in the CRI Attach implementation where a user can exhaust memory on the host due to goroutine leaks. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. To workaround this vulnerability, users can set up an admission controller to control accesses to pods/attach resources.
From the CVE record · GitHub_M
Affected containerd versions leak goroutines in the CRI Attach implementation. A user who can access pods/attach resources can exhaust host memory; the input does not specify whether authentication or additional user interaction is required.
Operators running containerd 1.7.28 or earlier, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4, or 2.2.0-beta.0 through 2.2.0-rc.1 should check their installations.