This the multi-page printable view of this section. Click here to print.
The table below summarizes the latest Kubernetes-to-containerd recommendations from the upstream containerd release policy.
| Kubernetes Version | Recommended containerd Version | CRI Version |
|---|---|---|
| 1.32 | 2.1.0+, 2.0.1+, 1.7.24+, 1.6.36+ | v1 |
| 1.33 | 2.1.0+, 2.0.4+, 1.7.24+, 1.6.36+ | v1 |
| 1.34 | 2.1.3+, 2.0.6+, 1.7.28+, 1.6.39+ | v1 |
| 1.35 | 2.2.0+, 2.1.5+, 1.7.28+ | v1 |
Vulnerability details Vulnerability details(official)
allowing otherwise unprivileged Linux users to traverse directory contents and execute programs.
When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files.
This vulnerability is rated as high-risk with a CVSS score of 7.2.
Ensure that the login users of the cluster nodes are all trusted users, and restrict the access rights of untrusted users to the cluster nodes. Remove unnecessary extended permissions in the container bundles directory.
This is the first fixed release by KLTS Containerd for v1.3.10.
Where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs.