Due to insecure handling of path traversal and the lack of path sanitization within unsquashfs
(a distribution provided utility used by Singularity), it is possible to overwrite/create any files on the host filesystem during the extraction of a crafted squashfs filesystem.
Squashfs extraction occurs automatically for unprivileged execution of Singularity (either --without-suid
installation or with allow setuid = no
) when a user attempts to run an image which:
library://
or shub://
Image build is also impacted in a more serious way as it is often performed by the root user, allowing an attacker to overwrite/create files leading to a system compromise. Bootstrap methods library
, shub
and localimage
trigger a squashfs extraction.
This issue is addressed in Singularity 3.6.4.
All users are advised to upgrade to 3.6.4 especially if they use Singularity mainly for building image as root user.
There is no solid workaround except to temporarily avoid use of unprivileged mode with single file images, in favor of sandbox images instead. Regarding image build, temporarily avoid building from library
and shub
sources, and as much as possible use --fakeroot
or a VM to limit potential impact.
General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:
Any sensitive security concerns should be directed to: security@sylabs.io
See our Security Policy here: https://sylabs.io/security-policy
{ "nvd_published_at": "2020-10-14T19:15:00Z", "github_reviewed_at": "2021-05-21T22:17:06Z", "severity": "HIGH", "github_reviewed": true, "cwe_ids": [ "CWE-22" ] }