CVE-2022-23648 Affecting containerd package, versions <1.5.11-150000.68.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.95% (84th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES150-CONTAINERD-2825397
  • published17 May 2022
  • disclosed16 May 2022

Introduced: 16 May 2022

CVE-2022-23648  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 containerd to version 1.5.11-150000.68.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream containerd package and not the containerd package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd’s CRI implementation on Linux with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.

CVSS Scores

version 3.1