x/vulndb: potential Go vuln in github.com/sylabs/singularity: GHSA-7gcp-w6ww-2xv9

[GoVulnBot]

In GitHub Security Advisory GHSA-7gcp-w6ww-2xv9, there is a vulnerability in the following Go packages or modules:

Unit	Fixed	Vulnerable Ranges
github.com/sylabs/singularity	3.6.4	>= 3.1.1, < 3.6.4

Cross references:

• CVE-2020-15229 appears in issue x/vulndb: potential Go vuln in github.com/sylabs/singularity: CVE-2020-15229, GHSA-7gcp-w6ww-2xv9 #900 NOT_IMPORTABLE
• GHSA-7gcp-w6ww-2xv9 appears in issue x/vulndb: potential Go vuln in github.com/sylabs/singularity: CVE-2020-15229, GHSA-7gcp-w6ww-2xv9 #900 NOT_IMPORTABLE

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: TODO
    versions:
      - introduced: 3.1.1
        fixed: 3.6.4
    packages:
      - package: github.com/sylabs/singularity
description: |-
    ### Impact

    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:

    - is a local SIF image or a single file containing a squashfs filesystem
    - is pulled from remote sources `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.

    ### Patches

    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.

    ### Workarounds

    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.

    ### For more information

    General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:

    * [Singularity Slack Channel](https://bit.ly/2m0g3lX)
    * [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)

    Any sensitive security concerns should be directed to: [email protected]

    See our Security Policy here: https://sylabs.io/security-policy
cves:
  - CVE-2020-15229
ghsas:
  - GHSA-7gcp-w6ww-2xv9

[tatianab]

Duplicate of #900