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/sing/<user>/<instance>. The manipulation of those files can change the behavior of the starter-suid program when instances are joined resulting in potential privilege escalation on the host.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Singularity | Sylabs | 3.1.0 (including) | 3.2.0 (excluding) |
| Singularity | Sylabs | 3.2.0 (including) | 3.2.0 (including) |
| Singularity | Sylabs | 3.2.0-rc1 (including) | 3.2.0-rc1 (including) |
| Singularity | Sylabs | 3.2.0-rc2 (including) | 3.2.0-rc2 (including) |