Incorrect Permission Assignment for Critical Resource Affecting containerd package, versions <1.4.11-56.1


Severity

Recommended
0.0
low
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.15% (53rd 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-2660186
  • published14 Apr 2022
  • disclosed25 Oct 2021

Introduced: 25 Oct 2021

CVE-2021-32760  (opens in a new tab)
CWE-732  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 containerd to version 1.4.11-56.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. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with specific files.

CVSS Scores

version 3.1