Summary
These are all security issues fixed in the singularity-3.8.3-1.2 package on the GA media of openSUSE Tumbleweed.
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Tumbleweed | singularity | 3.8.3-1.2 |
Vulnerabilities 12
-
High 8.8
Incorrect Permission Assignment for Critical Resource in Singularity
An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/s…
-
High 8.8
Insecure permissions on build temporary rootfs in Singularity
Sylabs Singularity through 3.6.2 has Insecure Permissions on temporary directories used in explicit and implicit container build operations, a different vulnerability than CVE-2020-25039.
-
High 8.2
Path traversal and files overwrite with unsquashfs
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 fi…
-
High 8.1
Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity
Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execution.
-
High 7.8
Sylabs Singularity Improper Input Validation
Sylabs Singularity 2.4 to 2.6 allows local users to conduct Improper Input Validation attacks.
-
High 7.5
Singularity insecure permissions
Insecure permissions (777) are set on $HOME/.singularity when it is newly created by Singularity (version from 3.3.0 to 3.5.1), which could lead to an information leak, and malicious redirection of operations performed against Sylabs cloud services.
-
High 7.5
Execution Control List (ECL) Is Insecure in Singularity
Sylabs Singularity 3.0 through 3.5 has Improper Validation of an Integrity Check Value. Image integrity is not validated when an ECL policy is enforced. The fingerprint required by the ECL is compared against the signature object descriptor(s) in the SIF file…
-
High 7.5
"Verify All" Returns Success Despite Validation Failures in Singularity
Sylabs Singularity 3.5.0 through 3.5.3 fails to report an error in a Status Code.
-
Medium 6.5
Singularity Incorrect Access Control
Singularity 2.3.0 through 2.5.1 is affected by an incorrect access control on systems supporting overlay file system. When using the overlay option, a malicious user may access sensitive information by exploiting a few specific Singularity features.
-
Medium 6.3
Action Commands (run/shell/exec) Against Library URIs Ignore Configured Remote Endpoint
Singularity is an open source container platform. In verions 3.7.2 and 3.7.3, Dde to incorrect use of a default URL, `singularity` action commands (`run`/`shell`/`exec`) specifying a container using a `library://` URI will always attempt to retrieve the conta…
-
Medium 5.5
Improper input validation in umoci
Open Container Initiative umoci before 0.4.7 allows attackers to overwrite arbitrary host paths via a crafted image that causes symlink traversal when "umoci unpack" or "umoci raw unpack" is used.
-
Unscored —
Sylabs Singularity 3.0 through 3.5 lacks support for an Integrity Check. Singularity's sign and verify commands do not …
References
-
web
https://www.suse.com/security/cve/CVE-2018-12021
-
web
https://www.suse.com/security/cve/CVE-2018-19295
-
web
https://www.suse.com/security/cve/CVE-2019-11328
-
web
https://www.suse.com/security/cve/CVE-2019-19724
-
web
https://www.suse.com/security/cve/CVE-2020-13845
-
web
https://www.suse.com/security/cve/CVE-2020-13846
-
web
https://www.suse.com/security/cve/CVE-2020-13847
-
web
https://www.suse.com/security/cve/CVE-2020-15229
-
web
https://www.suse.com/security/cve/CVE-2020-25039
-
web
https://www.suse.com/security/cve/CVE-2020-25040
-
web
https://www.suse.com/security/cve/CVE-2021-29136
-
web
https://www.suse.com/security/cve/CVE-2021-32635