Singularity: Incorrect path matching for 'limit container paths' directive
sylabs singularity · sylabs SingularityPRO
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sylabs/singularity/v4 Go |
|
|
| github.com/sylabs/singularity Go |
| No fix yet |
sylabs singularity · sylabs SingularityPRO
| Product | Affected | Fixed in |
|---|---|---|
| github.com/sylabs/singularity/v4 Go |
|
|
| github.com/sylabs/singularity Go |
| No fix yet |
SingularityCE and SingularityPRO are open source container platforms. Prior to SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14, incorrect path-string matching in the singularity.conf limit container paths directive allows a container in a sibling directory such as /data/safe-but-unsafe to be run when /data/safe is allowed under setuid mode. This permits a user to run a container from outside the administrator's configured path allowlist. Installations that do not use limit container paths are not affected. This issue is fixed in SingularityCE 4.4.2 and SingularityPRO 4.3.9 and 4.1.14.
From the CVE record · GitHub_M
Incorrect path matching in the singularity.conf limit container paths directive can allow a container in a sibling directory outside the configured allowlist to run. A local user can exploit this under setuid mode when the directive is in use; installations that do not use it are unaffected.
Check installations before SingularityCE 4.4.2 or SingularityPRO 4.3.9 and 4.1.14, Go github.com/sylabs/singularity/v4 versions below 4.4.2, and the github.com/sylabs/singularity package, for which no fixed version is listed.