p PatchFirst

CVE-2020-15229

CVE-2020-15229 · Path traversal and files overwrite with unsquashfs

CVSS 8.2 · High · EPSS 2.0% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

Check the installed version:

apk list -I -o singularity

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Singularity (an open source container platform) from version 3.1.1 through 3.6.3 has a vulnerability. Due to insecure handling of path traversal and the lack of path sanitization within `unsquashfs`, it is possible to overwrite/create any files on the host filesystem during the extraction with a crafted squashfs filesystem. The extraction occurs automatically for unprivileged (either installation or with `allow setuid = no`) run of Singularity when a user attempt to run an image which is a local SIF image or a single file containing a squashfs filesystem and is coming from remote sources `library://` or `shub://`. Image build is also impacted in a more serious way as it can be used by a root user, allowing an attacker to overwrite/create files leading to a system compromise, so far bootstrap methods `library`, `shub` and `localimage` are triggering the 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 temporary avoid to use unprivileged mode with single file images in favor of sandbox images instead. Regarding image build, temporary avoid to build from `library` and `shub` sources and as much as possible use `--fakeroot` or a VM for that.

Published
Updated

Fixes in distributions

Stack: system

Affected products and versions

  • singularity

    Versions
    • < 3.6.4: Affected

    No fix published

  • singularity Alpine 3.19

    Affected ranges
    • ECOSYSTEM: ≥ 3.1.1, < 3.6.4-r0

    Update to 3.6.4-r0

  • singularity Alpine 3.20

    Affected ranges
    • ECOSYSTEM: ≥ 3.1.1, < 3.6.4-r0

    Update to 3.6.4-r0

  • singularity Alpine 3.21

    Affected ranges
    • ECOSYSTEM: ≥ 3.1.1, < 3.6.4-r0

    Update to 3.6.4-r0

  • singularity Alpine 3.22

    Affected ranges
    • ECOSYSTEM: ≥ 3.1.1, < 3.6.4-r0

    Update to 3.6.4-r0

  • singularity Alpine 3.23

    Affected ranges
    • ECOSYSTEM: ≥ 3.1.1, < 3.6.4-r0

    Update to 3.6.4-r0

  • singularity Alpine 3.24

    Affected ranges
    • ECOSYSTEM: ≥ 3.1.1, < 3.6.4-r0

    Update to 3.6.4-r0

Original sources

Check your server →