A bug was found in containerd 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. Users should update to these versions as soon as they are released. Running containers do not need to be restarted.
Ensure you 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 unexpected files.
If you have any questions or comments about this advisory:
{ "nvd_published_at": "2021-07-19T21:15:00Z", "cwe_ids": [ "CWE-668", "CWE-732" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2021-07-22T20:21:14Z" }