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.
{ "nvd_published_at": "2019-05-14T21:29:00Z", "cwe_ids": [ "CWE-269", "CWE-732" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2021-05-17T15:50:05Z" }