cve.bz

CVE-2020-15229 Path traversal

9.3 criticalEPSS 2.0%Fix available

Critical (9.3). EPSS 2.0% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/sylabs/singularity 3.6.4.

On this page
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.

Severity

CVSS 3.1

9.3 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS
2.0% (unchanged from 2.0% a week ago; 2.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-15229 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-15229?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-15229?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-15229 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sylabs:singularityfrom 3.1.1 through 3.6.3
opensuse:backports_sle15.0:sp2
opensuse:leap15.1
opensuse:leap15.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7gcp-w6ww-2xv9Gogithub.com/sylabs/singularity>=3.1.1 <3.6.43.6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSEPackage Hub 15 SP2singularity3.6.4-bp152.2.12.1openSUSE-SU-2020:1814-1
openSUSELeap 15.1singularity3.6.4-lp151.2.12.1openSUSE-SU-2020:1769-1
openSUSELeap 15.2singularity3.6.4-lp152.2.9.1openSUSE-SU-2020:1770-1
openSUSETumbleweedsingularity3.8.3-1.2openSUSE-SU-2024:11384-1
Alpinev3.19, v3.20, v3.21 and 3 moresingularity3.6.4-r0ALPINE-CVE-2020-15229

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE · Alpine.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON